[SOLVED] Singularity error: Failed creating home directory in container
Linux - ContainersThis forum is for the discussion of all topics relating to Linux containers. Docker, LXC, LXD, runC, containerd, CoreOS, Kubernetes, Mesos, rkt, and all other Linux container platforms are welcome.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Singularity error: Failed creating home directory in container
Using Singularity, I have managed to build a container from DockerHub, shell it with Sudo, successfully installed some software, and even run it with Sudo. However, when I try to shell it as an unprivileged user, it gives me an error
Could someone help me in this? Thank you!
The error is as follows:
Code:
> singularity shell miniconda4
Increasing verbosity level (2)
Singularity version: 2.4.2-dist
Exec'ing: /usr/lib/x86_64-linux-gnu/singularity/cli/shell.exec
Evaluating args: 'miniconda4'
VERBOSE: Set messagelevel to: 2
VERBOSE: Initialize configuration file: /etc/singularity/singularity.conf
VERBOSE: Initializing Singularity Registry
VERBOSE: Invoking the user namespace
VERBOSE: Not virtualizing USER namespace: running as SUID
VERBOSE: No autofs bug path in configuration, skipping
VERBOSE: Using session directory: /var/lib/singularity/mnt/session
VERBOSE: Mounting overlay with options: lowerdir=/var/lib/singularity/mnt/container,upperdir=/var/lib/singularity/mnt/overlay/upper,workdir=/var/lib/singularity/mnt/overlay/work
VERBOSE: Running all mount components
VERBOSE: Binding '/etc/localtime' to '/var/lib/singularity/mnt/final//etc/localtime'
VERBOSE: Binding '/etc/hosts' to '/var/lib/singularity/mnt/final//etc/hosts'
VERBOSE: Bind-mounting host /proc
VERBOSE: Mounting /sys
VERBOSE: Bind mounting /dev
VERBOSE: Mounting home directory source into session directory: /home/AD/praposo -> /var/lib/singularity/mnt/session/home/AD/praposo
VERBOSE: Failed to create parent directory /var/lib/singularity/mnt/final/home/AD/praposo
ERROR : Failed creating home directory in container /var/lib/singularity/mnt/final/home/AD/praposo: Operation not supported
ABORT : Retval = 255
do you really want to create that directory in your container? (ERROR : Failed creating home directory in container /var/lib/singularity/mnt/final/home/AD/praposo: Operation not supported)
do you really want to create that directory in your container? (ERROR : Failed creating home directory in container /var/lib/singularity/mnt/final/home/AD/praposo: Operation not supported)
Hi. I don't wish to create the directory but it seems that just by 'shelling' the container using singularity, it automatically attempts to create it. Maybe it attempts to mount the home of the user (?), but I don't know.
I would rather say you have misconfigured something. I don't think you really need that dir.
Thank you pan64 ! You made me think of the problem in a different way. I figured out that by using the '--writable' option in the 'singularity shell' command, it allows any user to create directories. Maybe you're right and I don't need to create that directory but I don't know how not to, since it tries to do it by itself. But we found a solution to this, so I'm going to close this thread.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.