Open wmwv opened 3 months ago
Hi @wmwv desc-stack-weekly is a shifter container without ssh. The primary purpose of the containers has been to provide a runtime environment rather than a full featured virtual machine. I'm not sure we need ssh from within the containers themselves (but could be coaxed into considering it). Can you just ssh to a NERSC login node from another terminal? I usually use NX when I connect to NERSC, where it's not a big deal to just open another terminal. Take care, Heather
Sure. Won't fix is a fine answer in practice.
I think it was confusing that it triggered a GLIBC version mismatch. I thought loading the image with shifter
would completely override existing paths.
FWIW, the image does have ssh
.
[login22 ~] start-kernel-cli.py desc-stack-weekly
[login22 ~] whereis ssh
ssh: /usr/bin/ssh /etc/ssh /opt/udiImage/bin/ssh
So /usr/bin/ssh
remains in the path, but the GLIBC is no longer for correct for it. Here's the tail of the path (after all of the /opt/lsst
) entries:
/opt/udiImage/modules/gpu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/udiImage/bin
If you explicitly run /opt/udiImage/bin/ssh
, that works fine.
This issue is stale because it has been 90 days since last activity.
If no further activities take place, this issue will be closed in 14 days.
Add label keep
to keep this issue.
Description A clear and concise description of what the issue is.
ssh
doesn't work for me in thedesc-stack-weekly
environment loaded from command line.If I use
start-kernel-cli.py
to loaddesc-stack-weekly
, and then try to ssh to another node (to, e.g., monitor load, GPU usage...), I getChoose all applicable topics by placing an 'X' between the [ ]:
To Reproduce