unable to start enroot container
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
- linux, shell
- Domain
- cli, devops, operating-systems
Research direction
Start by reproducing enroot start test after running ./enroot-check_3.5.0_x86_64.run. Inspect the failure from /etc/enroot/hooks.d/98-nvidia.sh and the reported /proc/self/ns/mnt permission error, then compare the environment with the requirements document. Done means identifying the missing permission or configuration and documenting a verified resolution.
Written by the indexing model from the issue text.
Description
i am facing issue while starting the enroot container.
i tried running the script shared in requirement doc to check if all the pre requisites are met. i dont see any issue there, yet i see this issue. can you please let me know if there is anything missing?
earlier i used to get the following error
[INFO] Extracting squashfs filesystem...
Parallel unsquashfs: Using 4 processors
425 inodes (144 blocks) to write
[===========================================================================================================================================================================|] 569/569 100%
created 90 files
created 98 directories
created 335 symlinks
created 0 devices
created 0 fifos
created 0 sockets
created 0 hardlinks
enroot-nsenter: failed to create user namespace: Permission denied
this got resolve by adding "unprivileged_userns" apparmor in complain mode.
i am running the check from requirements doc and seems to be fine.
./enroot-check_3.5.0_x86_64.run
Extracting [####################] 100%
Bundle ran successfully!
but enroot start gives this error.
enroot start test
nvidia-container-cli: initialization error: open failed: /proc/self/ns/mnt: permission denied
[ERROR] /etc/enroot/hooks.d/98-nvidia.sh exited with return code 1
can you please let me know if there is anything missing?
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 139
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/enroot
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Update Vish to 1.1.5 Openpackage-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oSoWoSo/vOid_Community_repOsitory#144 · 1 comment ·
-
help wanted new command
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tldr-pages/tldr#24151 ·
-
PacReq: Rune IDE Openpackage request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pacstall/pacstall-programs#9402 ·
-
[BUG] ci: the first prefetch-images.sh call runs before shard.txt exists, so it is always a no-op Openbug github-actions
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
update-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
msys2/MINGW-packages#31768 ·