-
-
Notifications
You must be signed in to change notification settings - Fork 52
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 #932
Comments
I got the same issue when pulling curlimages/curl |
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? |
Sorry, I was replying on the previous @BrandonStudio comment on As for the issue itself, I am using recomended docker installation instruction for Ubuntu Jammy and I cannot reproduce your issue:
|
Thank you @suricactus |
news?
|
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. |
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. |
Closing this issue as it is only affecting very specific environments. |
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.:
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.
The text was updated successfully, but these errors were encountered: