You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When importing a docker image I expect file permissions to be applied correctly.
Actual behavior
If a Docker image is imported that was built such that a files permissions are changed in a separate layer than the file was originally created in the permissions when running under Singularity are incorrect.
Steps to reproduce behavior
Dockerfile
FROM ubuntu
RUN mkdir -m 700 /foobar
RUN chmod a+rx /foobar
From what I can tell this looks to be an issue with opencontainers/image-tools which is used to create the bundle. I've created opencontainers/image-tools#218 to track this.
Thanks for the update @AdamSimpson. Looks like @cyphar thinks we should be using umoci. Might be useful to do some research on what it would take to make that change.
Version of Singularity:
v3.2.1
Expected behavior
When importing a docker image I expect file permissions to be applied correctly.
Actual behavior
If a Docker image is imported that was built such that a files permissions are changed in a separate layer than the file was originally created in the permissions when running under Singularity are incorrect.
Steps to reproduce behavior
Dockerfile
Docker image created with correct permissions
Running under Singularity shows the incorrect permissions
The text was updated successfully, but these errors were encountered: