![]() See more about host mounts with SELinux at Configure the selinux label.įor others that see this issue with containers running as a different user, you need to ensure the UID/GID of the user inside the container has permissions to the file on the host. Your volume mount command would then look like: sudo docker run -i -v /data1/Downloads:/Downloads:z ubuntu bash The Z option indicates that the bind mount content is private and unshared.The z option indicates that the bind mount content is shared among multiple containers.When using a host mount with SELinux, you need to pass an extra option to the end of the volume definition: The dot at the end of the permission string, drwxr-xr-x., indicates SELinux is configured. However, this specific case is different. Typically, permissions issues with a host volume mount are because the UID/ GID inside the container does not have access to the file according to the UID/GID permissions of the file on the host.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |