SOS! Help! I cannot get enroot/pyxis to work: error: pyxis: error: a container with name "pyxis_nemo-25.07.gpt_oss" does not exist, and --container-image is not set

Open
#249 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
shell
Domain
cli, tooling

Research direction

Start by reproducing the reported enroot import, create, list, and srun commands with the shown ENROOT_DATA_PATH and container names. Trace how pyxis resolves the --container-name value against the enroot containers, and consider the issue complete when the cause of the name mismatch is identified and documented or corrected with a verified srun invocation.

Written by the indexing model from the issue text.

Description

Hi there,

SOS! Could you please kindly help me? I just couldn't get pyxis work:

Thanks!


enroot import 'docker://nvcr.io#nvidia/nemo:25.07.gpt_oss'

enroot create --name pyxis_nemo-25.07.gpt_oss nvidia+nemo+25.07.gpt_oss.sqsh

And then since then I updated one of the sub-folders inside the container slightly by using the latest repo main branch, so I am not willing to directly to pull from NVIDIA registry in srun.

mike@ln01:~/enroot$ enroot list
cache
data
nemo-25.04
pyxis_hiyouga
pyxis_nemo-25.07.gpt_oss
pyxis_nemo-25.07.gpt_oss.sqsh
mike@ln01:~/enroot$ enroot version
3.5.0
mike@ln01:~/enroot$ ll
total 15122412
drwxr-xr-x 2 mike domain users        4096 Sep 25 17:05 ./
drwx------ 2 mike domain users        4096 Sep 25 16:43 ../
drwx------ 2 mike domain users        4096 Jun 30 11:48 cache/
drwx------ 2 mike domain users        4096 Sep 25 16:21 data/
drwxr-xr-x 2 mike domain users        4096 Jul 14 01:33 nemo-25.04/
drwxr-xr-x 2 mike domain users        4096 May 11 03:21 pyxis_hiyouga/
drwxrwxrwx 2 mike domain users        4096 Sep 21 17:57 pyxis_nemo-25.07.gpt_oss/
-rw-r----- 1 mike domain users 15485349888 Sep 24 22:53 pyxis_nemo-25.07.gpt_oss.sqsh


**mike@ln01:~/enroot$ srun --partition=gpu-interactive --account=gpu   --container-name="nemo-25.07.gpt_oss"   /bin/hostname**
srun: job 1276806 queued and waiting for resources
srun: job 1276806 has been allocated resources
slurmstepd-gn12: error: pyxis: error: a container with name "pyxis_nemo-25.07.gpt_oss" does not exist, and --container-image is not set
slurmstepd-gn12: error: spank: required plugin spank_pyxis.so: task_init() failed with rc=-1
slurmstepd-gn12: error: Failed to invoke spank plugin stack
srun: error: gn12: task 0: Exited with exit code 1



mike@ln01:~/enroot$ ll
total 15122412
drwxr-xr-x 2 mike domain users        4096 Sep 25 17:26 ./
drwx------ 2 mike domain users        4096 Sep 25 16:43 ../
drwx------ 2 mike domain users        4096 Jun 30 11:48 cache/
drwx------ 2 mike domain users        4096 Sep 25 16:21 data/
drwxr-xr-x 2 mike domain users        4096 Jul 14 01:33 nemo-25.04/
drwxr-xr-x 2 mike domain users        4096 May 11 03:21 pyxis_hiyouga/
drwxrwxrwx 2 mike domain users        4096 Sep 21 17:57 pyxis_nemo-25.07.gpt_oss/
-rw-r----- 1 mike domain users 15485349888 Sep 24 22:53 pyxis_nemo-25.07.gpt_oss.sqsh
mike@ln01:~/enroot$ echo $ENROOT_DATA_PATH 
/home/mike/enroot

Dominant language
Shell
Stars
1.1k
Forks
139
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/enroot

All issues in NVIDIA/enroot

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.