-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Can't pull container. failed to register layer: lsetxattr user.overlay.impure /etc: operation not supported #55
Comments
What command-line are you running that gives you this error?
|
I'm using Bash inside an Ubuntu 23.04 LXC. I uninstalled all native docker tools and installed the official engine according to the docker installation guide |
Please tell us what you typed in bash before seeing that error.
|
|
Are you running Docker inside a Docker container? I could see that causing
problems. In any case, this looks like a local configuration problem to me. It
works fine on my system:
$ docker pull curlimages/curl
Using default tag: latest
latest: Pulling from curlimages/curl
Digest: sha256:25d29daeb9b14b89e2fa8cc17c70e4b188bca1466086907c2d9a4b56b59d8e21
Status: Image is up to date for curlimages/curl:latest
docker.io/curlimages/curl:latest
$ docker pull quay.io/curl/curl:latest
latest: Pulling from curl/curl
Digest: sha256:1e136d717aab088c1f157ff816cf4219fe457a1687f11580e6a127488954f67f
Status: Downloaded newer image for quay.io/curl/curl:latest
quay.io/curl/curl:latest
|
Hmm interesting. I didn't touch a thing about the container. It's a LXC Ubuntu 23.04 on Proxmox VE. I changed nothing besides running an Which version of the docker engine are you running? I'm on 25.0.2
The link I provided in my first message suggests that it's an issue of Docker v25 breaking something and the fix is on the container side. |
Btw thanks a lot for your quick help |
https://docs.docker.com/engine/release-notes/25.0/#extended-attributes-for-tar-files Do you use tar archives that were created on MacOS? The docker release notes seem to blame the MacOS tar implementation |
cannot repro ... you might also try running podman |
Same issue. |
I see the same issue. The latest release that works is 8.1.1. Every release that I have tested after that has this problem. |
are you (@Furisto ) also on ubuntu ? |
I see the same issue, I'm using a brand new workspace in gitpod |
so ubuntu it is then, will take a deeper look |
Thanks, I forgot to report the docker version docker --version The pull is working fine with 7.88.1 version |
This issue is between docker (some version) and ubuntu (some version) ... we have not made any changes in terms of the container itself and more about how buildah does things ... the problem is that latest docker no longer ignores a certain class of errors and we need to rebuild using an updated version of buildah (containers/buildah@662908f). In the short term, one can rollback to some older version of docker or use podman ... will refresh the buildah toolchain and arrange a new release which will hopefully address. |
Thanks a lot for taking the time to look into it. Feel free to ping me so I can tell you if it's fixed when you're ready |
does the latest release fix things for you ? |
$ docker pull curlimages/curl:latest
latest: Pulling from curlimages/curl
4abcf2066143: Pull complete
e52d86b3391d: Extracting [==================================================>] 7.111MB/7.111MB
4ca545ee6d5d: Download complete
failed to register layer: lsetxattr user.overlay.origin /bin: operation not supported It seems something has changed? Is that a good news? |
Is there any reason to believe this would be a problem specifically with buildx / buildkit? I have issues with the curl image inside a multi-stage Dockerfile - but only since buildkit 0.17.0 released a few days ago (i.e Running within a dind environment with rootless buildkit builder, host kernel |
Title pretty much says everything. As it seems this issue is with the container.
They seem to have found a solution here
Other containers pull fine for me.
The text was updated successfully, but these errors were encountered: