Can't pull container. failed to register layer: lsetxattr user.overlay.impure /etc: operation not supported
Cris70 opened this issue · comments
I have been following the istructions, but when I get to the "docker compose up -d --build" instruction, I always get the error in the subject (not immediately, after some work has been done).
e.g.:
[+] Running 9/12
⠙ mkcert 8 layers [⣿⣿⠀⣿⣿⣿⣿⣿] 16.14MB/155.5MB Pulling 15.2s
✔ a0710691c81a Pull complete 0.7s
✔ 8ca9a27aacf4 Pull complete 0.5s
⠋ e568633f0bc3 Downloading [=====> ] 16.14MB... 14.0s
✔ 02dfb441bace Download complete 1.3s
✔ 560ed5ef524c Download complete 11.2s
✔ 55530a19410e Download complete 11.3s
✔ 26d527d9526a Download complete 13.2s
✔ 14682b532053 Download complete 12.0s
⠙ mirror_transformation_grids 2 layers [⣿⣿] 0B/0B Pulling 15.2s
✔ c158987b0551 Pull complete 11.9s
✔ 25c404220482 Download complete 12.9s
failed to register layer: lsetxattr user.overlay.impure /etc: operation not supported
I've seen elsewhere that the problem seems to have surfaced with docker releases > 25.
I'm using docker 26 on Rocky Linux 9.3.
I got the same issue when pulling curlimages/curl
Looks like an upstream problem curl/curl-container#55
Looks like an upstream problem curl/curl-container#55
I'm sorry but I don't see anything in that thread that justifies your statement. Can you please point me to the exact comment?
What I'm starting to see, instead, is that all those experiencing this problem are using docker on a Proxmox LXC (me included).
Maybe this is where the problem lies.
Sorry, I was replying on the previous @BrandonStudio comment on curl .
As for the issue itself, I am using recomended docker installation instruction for Ubuntu Jammy and I cannot reproduce your issue:
$ docker --version
Docker version 25.0.2, build 29cf629
Thank you @suricactus
I'll do some tests on a normal Proxmox VM and will report back.
news?
i have same error in CT of proxmox
Thank you @suricactus I'll do some tests on a normal Proxmox VM and will report back.
news? i have same error in CT of proxmox
Sorry @ilgio, I have not yet had time to test it.
The QFieldCloud project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.
news? i have same error in CT of proxmox
Thank you @suricactus I'll do some tests on a normal Proxmox VM and will report back.
I used a normal VM and it worked without problems.
The QFieldCloud project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale". If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.
Closing this issue as it is only affecting very specific environments.