-
Notifications
You must be signed in to change notification settings - Fork 18.9k
vendor: BuildKit 950603da215ae03b843f3f66fbe86c4876a6f5a1 #41745
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
vendor.conf
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see a change in go.mod for buildkit, which is still at 0edc412565dc - perhaps do this separate?
|
CI seems hitting a regression? |
|
Regression introduced in moby/buildkit@174bcf8 (moby/buildkit#1862) |
|
I opened moby/buildkit#1874 to revert the change |
|
@AkihiroSuda Looks like the only containerd changes potentially affecting docker are containerd/containerd@126b35ca4 and containerd/containerd@fd01744a0. I'd rather get in the buildkit vendor to get the fix in, but I don't think it's that important to have containerd dependency update for this next release. We can update containerd dependencies here and in buildkit when we need it. Let me know if I'm missing something. |
ae52cc7 to
f92d74d
Compare
|
Updated to bring in the new buildkit fix from moby/buildkit#1874 and reverted the containerd bump in this PR. |
vendor.conf
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like you removed the comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think i mixed the two, i wanted to remove it for buildkit not containerd.
vendor.conf
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there's no v0.8 branch yet, so wondering if this would be v0.8.1-dev ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
generally speaking I believe -dev is not derived from patch number versions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that's correct, this is more of a "manual" indication; alternatively v0.8.0-4-g950603da;
git checkout 950603da215ae03b843f3f66fbe86c4876a6f5a1
git describe --tags --match 'v*'
v0.8.0-4-g950603daSigned-off-by: Akihiro Suda <[email protected]> Signed-off-by: Tibor Vass <[email protected]>
f92d74d to
34682e5
Compare
AkihiroSuda
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @tiborvass @thaJeztah
LGTM, bu I can't click "Approve" because this PR was initially my own
|
Hello, I've just ran "apt-get upgrade" on my CI, which upgraded docker to "Docker version 20.10.0, build 7287ab3". Probably the original commit made it into the release, but not the revert ? Or maybe it's just the packages on the apt repository which haven't been updated ? I'm installing from I'll revert to 19.03 for now. Thanks |
|
@lbndev can you open a ticket with full output of Trying to reproduce, but I don't see this problem; DOCKER_BUILDKIT=1 docker build -t foo -<<'EOF'
FROM busybox
ENTRYPOINT []
EOF
[+] Building 0.1s (5/5) FINISHED
=> [internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 64B 0.0s
=> [internal] load .dockerignore 0.0s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/busybox:latest 0.0s
=> [1/1] FROM docker.io/library/busybox 0.0s
=> => resolve docker.io/library/busybox:latest 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:c6301af1809013800e3d2fefe42a9a469ddd828bbfe61a23d84dc25f08c9a731 0.0s
=> => naming to docker.io/library/foo 0.0s
DOCKER_BUILDKIT=0 docker build -t foo -<<'EOF'
FROM busybox
ENTRYPOINT []
EOF
Sending build context to Docker daemon 2.048kB
Step 1/2 : FROM busybox
---> 1c35c4412082
Step 2/2 : ENTRYPOINT []
---> Running in e6263564cd8a
Removing intermediate container e6263564cd8a
---> 0fe82f88eb6e
Successfully built 0fe82f88eb6e
Successfully tagged foo:latest |
Done. Please see #41770. |
Follow-up to #41688.
Also updates containerd: #41688 (comment)EDIT: by @tiborvass, see #41745 (comment)