Hi,
I've been trying to ssh into a running enroot container on our SLURM cluster via Pyxis/Enroot. I'd like to be able to access the running container, which is running on our cluster, from my local machine, and more importantly, access it using an IDE.
Looking within the container, I found that the /etc/passwd and /etc/shadow files were marked with an 'x' for the user that submitted the job in the first place, so I can't login using a password.
My question is: Is this by design?
I was expecting to be able to login with the same username/password as for the controller node.
Eventually, I was able to access the running container by adding ssh keys to the shared nfs folder, but I was wondering whether it was possible to access the containers through password as well.
Hi, I've been trying to ssh into a running enroot container on our SLURM cluster via Pyxis/Enroot. I'd like to be able to access the running container, which is running on our cluster, from my local machine, and more importantly, access it using an IDE.
After submitting the job using
srun --ntasks=1 --gpus-per-task=1 --gpus=1 --container-mounts=/data/pathology:/data/pathology --no-container-remap-root --container-image=${CONTAINER_IMAGE} --pty bash
I was able to start the sshd service in the container using
/usr/sbin/sshd -p 2222
However, trying to access the enroot container through my local machine on port 2222 yielded:
Looking within the container, I found that the /etc/passwd and /etc/shadow files were marked with an 'x' for the user that submitted the job in the first place, so I can't login using a password.
My question is: Is this by design? I was expecting to be able to login with the same username/password as for the controller node.
Eventually, I was able to access the running container by adding ssh keys to the shared nfs folder, but I was wondering whether it was possible to access the containers through password as well.