-
Notifications
You must be signed in to change notification settings - Fork 97
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
permission denied in unpriv.create when creating rootless image #222
Comments
First off, cool. 😸 I think this is happening because the mode of |
I just realised that these two possible options have different semantics in the case of hard-linked files (which the spec doesn't help clarify). If you have a hard-linked file, and then you have a new layer that modifies the file, should the other hard-links see the modifications? In theory, the new layer should have |
I've gone with the removal option in #223. PTAL and double-check it fixes the issue (that patch fixed the issue on my machine). |
Thanks @cyphar for the very quick turn-around. I'll try to check this later today. L |
@cyphar any ETA on the 0.4.0 release? Thanks. |
https://github.com/openSUSE/umoci/milestone/9 tracks the remaining issues I would like to fix before |
Hi,
we're trying to test the skopeo / umoci / runc toolchain for usage within high energy physics usecases (ATLAS experiment). We publish images on Docker Hub that we'd like to run in rootless mode
hub.docker.com/r/atlas/
but unpacking them with umoci hrows this error (unpacking e.g. busybox works fine)
steps to reproduce
any pointers what could be amiss?
(cc'ing @davidlt)
The text was updated successfully, but these errors were encountered: