Skip to content
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

Open
Gabgobie opened this issue Apr 15, 2024 · 20 comments
Assignees

Comments

@Gabgobie
Copy link

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.

@dfandrich
Copy link

dfandrich commented Apr 15, 2024 via email

@Gabgobie
Copy link
Author

Gabgobie commented Apr 15, 2024

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

@dfandrich
Copy link

dfandrich commented Apr 15, 2024 via email

@Gabgobie
Copy link
Author

Gabgobie commented Apr 15, 2024

docker pull <image>

root@docker-temp:~# docker pull curlimages/curl
Using default tag: latest
latest: Pulling from curlimages/curl
4abcf2066143: Already exists
1113023ab841: Extracting [==================================================>]  4.308MB/4.308MB
4ca545ee6d5d: Download complete
failed to register layer: lsetxattr user.overlay.impure /etc: operation not supported
root@docker-temp:~# docker pull quay.io/curl/curl:latest
latest: Pulling from curl/curl
b6f1a98f98c5: Already exists
1113023ab841: Extracting [==================================================>]  4.308MB/4.308MB
4ca545ee6d5d: Download complete
failed to register layer: lsetxattr user.overlay.impure /etc: operation not supported
root@docker-temp:~#

@dfandrich
Copy link

dfandrich commented Apr 15, 2024 via email

@Gabgobie
Copy link
Author

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 apt update && apt full-upgrade -y and following the docker engine install guide to get a clean system -> using the docker.com repo.

Which version of the docker engine are you running? I'm on 25.0.2

root@docker-temp:~/plexdownloads# docker -v
Docker version 25.0.2, build 29cf629

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.

@Gabgobie
Copy link
Author

Btw thanks a lot for your quick help

@Gabgobie
Copy link
Author

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

@xquery
Copy link
Member

xquery commented Apr 16, 2024

cannot repro ... you might also try running podman

@BrandonStudio
Copy link

Same issue.
I'm on Ubuntu 22.04 with rootless docker.
It works fine when I pull 7.88.1 but fails when I pull latest.
I have not tested other version.

@Furisto
Copy link

Furisto commented Apr 25, 2024

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.

@xquery
Copy link
Member

xquery commented Apr 25, 2024

are you (@Furisto ) also on ubuntu ?

@aquarta
Copy link

aquarta commented Apr 27, 2024

I see the same issue, I'm using a brand new workspace in gitpod
Linux fiware-tutorialsiotsens-r1iaycrgx85 6.1.75-060175-generic #202402010024 SMP PREEMPT_DYNAMIC Thu Feb 1 01:44:23 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.4 LTS"

@xquery xquery self-assigned this Apr 28, 2024
@xquery
Copy link
Member

xquery commented Apr 28, 2024

so ubuntu it is then, will take a deeper look

@aquarta
Copy link

aquarta commented Apr 28, 2024

Thanks, I forgot to report the docker version

docker --version
Docker version 26.0.1, build d260a54

The pull is working fine with 7.88.1 version

@xquery
Copy link
Member

xquery commented Apr 29, 2024

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.

@Gabgobie
Copy link
Author

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

@xquery
Copy link
Member

xquery commented Jun 14, 2024

does the latest release fix things for you ?

@BrandonStudio
Copy link

BrandonStudio commented Jun 14, 2024

$ 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?

@chadlwilson
Copy link

chadlwilson commented Nov 4, 2024

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 0.16.0 is OK)

Running within a dind environment with rootless buildkit builder, host kernel Linux 5.10.219-208.866.amzn2.x86_64 amd64.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants