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
Fails to bind/mount a non existing dir in container #756
Comments
hey @osallou ! Could you please provide output with
(I apologize I know that's the worst message "hey it works for me!" but with debug we can start to figure out what is going on |
I think that |
could indeed by centos6 related , but many clusters/hpc do not have recent OS... :-( |
I just ran into the same issue on a RHEL6.9-based cluster. overlayfs is actually supported in RHEL 7.1 as a tech preview only, so while it could work on a RHEL/CentOS 7-based host, it won't with a standard CentOS/RHEL 6 kernel, doh. Is there another way to do custom bind if files don't exist in the container? |
Closing this - as noted overlay is not present on CentOS/RHEL6. If you need to bind into a container you will need to add the directory bind point to the container by building a new image, with |
Version of Singularity:
2.3-dist
Expected behavior
Have in conf user bind control and enable overlay to yes
Expect to mount a local directory in container even if it does not exists in container
I am on CentOS 6.7
Actual behavior
as options are set as per doc explained, user should be able to mount a non existant directory in container.
Steps to reproduce behavior
The text was updated successfully, but these errors were encountered: