-
Notifications
You must be signed in to change notification settings - Fork 509
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
"imagetools create" panics when pushing the created image (episode 2) #2232
Comments
I think that I've a better understanding of what is causing this bug and #2229. I fixed a mistake in the CI that was making |
Thanks for your feedback but it should not panic anyway 😇. We updated otel dependencies in #2281 which might fix the otel issue. If you still repro, you can try with: -
name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
with:
version: "https://github.com/docker/buildx.git#5723ceefb6a52e16339acfed86871ffdabf240a7" Otherwise feel free to close this issue, thanks! |
I am not quite sure if it's the same issue, but I am running into a I get a The underlying issue seems to be related to how buildx interacts with panic: send on closed channel
goroutine 7797 [running]:
github.com/containerd/containerd/remotes/docker.(*pushWriter).setPipe(...)
github.com/containerd/containerd@v1.7.13/remotes/docker/pusher.go:364
github.com/containerd/containerd/remotes/docker.dockerPusher.push.func1()
github.com/containerd/containerd@v1.7.13/remotes/docker/pusher.go:286 +0x12a
github.com/containerd/containerd/remotes/docker.(*request).do(0xc002c4a240, {0x276fc58, 0xc000e7ce10})
github.com/containerd/containerd@v1.7.13/remotes/docker/resolver.go:556 +0x162
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries(0x0?, {0x276fc58, 0xc000e7ce10}, {0xc0006a10e0, 0x1, 0x1})
github.com/containerd/containerd@v1.7.13/remotes/docker/resolver.go:600 +0x[45](https://github.com/nginxinc/docker-nginx-unprivileged/actions/runs/8111951034/job/22172780476#step:9:46)
github.com/containerd/containerd/remotes/docker.(*request).doWithRetries(0x0?, {0x276fc58, 0xc000e7ce10}, {0x0, 0x0, 0x0})
github.com/containerd/containerd@v1.7.13/remotes/docker/resolver.go:613 +0x12d
github.com/containerd/containerd/remotes/docker.dockerPusher.push.func2()
github.com/containerd/containerd@v1.7.13/remotes/docker/pusher.go:292 +0x45
created by github.com/containerd/containerd/remotes/docker.dockerPusher.push in goroutine 11[54](https://github.com/nginxinc/docker-nginx-unprivileged/actions/runs/8111951034/job/22172780476#step:9:55)
github.com/containerd/containerd@v1.7.13/remotes/docker/pusher.go:291 +0x21ad
Error: Process completed with exit code 2. |
@alessfg The docker pusher issue might have been fixed with containerd/containerd#8379 (cc @jedevc) but I don't see it backported to container 1.7 branch yet. |
Opened a backport in containerd/containerd#9921. |
@jedevc Is this related to this OTEL panic? I also opened open-telemetry/opentelemetry-go-contrib#5187 but does not seem to be moving. |
I think @alessfg's issue is likely separate, the upstream OTEL PR looks like the way to go for now. |
Yup I ran into OTEL issues a couple times but they seem to have gone away when I started using the latest changes in |
I was looking at the trace from first comment, did not notice that #2232 (comment) was different. |
Thanks! |
Contributing guidelines
I've found a bug and checked that ...
Description
#2230 fixes the initial bug (#2229) but sometimes triggers another panic related to opentelemetry (#2230 (comment)).
Expected behaviour
No crash.
Actual behaviour
Buildx version
github.com/docker/buildx 95bdecc 95bdecc
Docker info
Builders list
Configuration
Bake definition: https://github.com/dunglas/frankenphp/blob/main/docker-bake.hcl (Dockerfiles in the same repo).
Build logs
Additional info
Full logs: https://github.com/dunglas/frankenphp/actions/runs/7728429011/job/21072578318
The text was updated successfully, but these errors were encountered: