enroot list -f does not work properly with NFS

Open
#242 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
shell
Domain
cli

Research direction

Reproduce enroot list -f with ENROOT_RUNTIME_PATH, ENROOT_CACHE_PATH, and ENROOT_DATA_PATH on an NFS volume under RHEL 8, then inspect the implementation of the enroot list -f command. Done means the container name is displayed instead of <unknown> for NFS-backed paths while local-volume behavior remains correct.

Written by the indexing model from the issue text.

Description

enroot list -f output displays when container is located on an NFS volume. i.e. ENROOT_RUNTIME_PATH, ENROOT_CACHE_PATH, and ENROOT_DATA_PATH are set to a location on an NFS volume.

[username@node ~]$ enroot list -f NAME PID COMM STATE STARTED TIME MNTNS USERNS COMMAND ubuntu24 <unknown> 1016787 bash S+ 10:52 00:03 4026533122 4026533121 bash

If the container is located on a local volume, i.e. ENROOT_RUNTIME_PATH, ENROOT_CACHE_PATH, and ENROOT_DATA_PATH are set to a location on a local volume.

[username@node ~]$ enroot list -f NAME PID COMM STATE STARTED TIME MNTNS USERNS COMMAND ubuntu24 1019234 bash S+ 10:55 00:05 4026533122 4026533121 bash

This issue occurs on RHEL 8.

Dominant language
Shell
Stars
1.1k
Forks
139
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.