Skip to content
Snippets Groups Projects

Resolve "Ddeploy job failing when enforcing labels"

1 unresolved thread

Closes #52 (closed)

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
30 30
31 31 # generate new image
32 32 if [ -n "${label_args+x}" ]; then
33 run_command="echo \"FROM $image_name\" | docker build $label_args -t $image_name -"
33 run_command="echo \"FROM $image_name\" | DOCKER_BUILDKIT=0 docker build $label_args -t $image_name --pull=false -"
  • added 1 commit

    • 0536cf0a - Allow changing branch from which pulling enforce_labels

    Compare with previous version

  • Iñigo Moreno i Caireta marked this merge request as ready

    marked this merge request as ready

  • added 1 commit

    Compare with previous version

  • requested review from @miguel.prada

  • added 1 commit

    Compare with previous version

  • Prada Sarasola, Miguel mentioned in merge request !84 (merged)

    mentioned in merge request !84 (merged)

  • This message is printed when running a build with DOCKER_BUILDKIT=0.

    DEPRECATED: The legacy builder is deprecated and will be removed in a future release.
                BuildKit is currently disabled; enable it by removing the DOCKER_BUILDKIT=0
                environment-variable.

    Using the full image name instead of the ID seems to also fix the problem, even when using BuildKit, see !84 (merged).

    See a related test job here (it fails because I hadn't realized there were more uses of DOCKER_ID, hopefully this other job "passes").

  • Please register or sign in to reply
    Loading