-
Notifications
You must be signed in to change notification settings - Fork 47
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
failed to register layer: lsetxattr user.overlay.impure /etc: operation not supported #56
Comments
Do other containers work for you? It looks to me like your docker daemon is unable to write layers correctly. |
This image is using buildah for building the image that is causing a problem in dockerd 25.0+ (https://docs.docker.com/engine/release-notes/25.0/#extended-attributes-for-tar-files) Fixed as of
ubuntu22.04 won't get the update, I'm building it from source to use it on GitHub Actions |
I have the same problem, is there a simple solution as I'm just starting out with docker, portainer etc.? |
A have also the same problem ! |
dumb question but can I use a dockerd < version 25.0 to avoid this problem as a workaround? |
Yes you can do that, dockerd <= 24.x are ignoring these errors and let you pull affected images. Only tested by me with different images that had the same error in dockerd 25.x |
I moved the build action from buildah to buildx as part of my latest release. Let me know if this works better. |
Hey there,
i am relatively new to the docker party and tried to use your description to set up a docker container with docker compose or docker, tried both. I get the same error in docker or docker compose:
[+] Running 2/3 ⠴ enshrouded-dedicated-server 2 layers [⣿⣿] ✔ 2f44b7a888fa Pull complete ✔ 980609f7b193 Download complete failed to register layer: lsetxattr user.overlay.impure /etc: operation not supported
I am aware that it's maybe an issue of my system enviroment, I use proxmox with a docker lxc.
If it's totally unrelated to your work, please close this. If you have a hint for me, It would be really appreciated :)
Great work by the way!!!
The text was updated successfully, but these errors were encountered: