enroot issue with installation inside #216
Comments
|
luzhang@dc7nvdgxluna001: |
|
Use the $ enroot start --help
Usage: enroot start [options] [--] NAME|IMAGE [COMMAND] [ARG...]
Start a container and invoke the command script within its root filesystem.
Command and arguments are passed to the script as input parameters.
In the absence of a command script and if a command was given, it will be executed directly.
Otherwise, an interactive shell will be started within the container.
Options:
-c, --conf CONFIG Specify a configuration script to run before the container starts
-e, --env KEY[=VAL] Export an environment variable inside the container
--rc SCRIPT Override the command script inside the container
-r, --root Ask to be remapped to root inside the container
-w, --rw Make the container root filesystem writable
-m, --mount FSTAB Perform a mount from the host inside the container (colon-separated) |
|
Thank you very much. The suggestion works !
From: Felix Abecassis ***@***.***>
Date: Tuesday, October 29, 2024 at 7:02 PM
To: NVIDIA/enroot ***@***.***>
Cc: Lucy Zhang ***@***.***>, Author ***@***.***>
Subject: Re: [NVIDIA/enroot] enroot issue with installation inside (Issue #216)
Use the --rw argument:
$ enroot start --help
Usage: enroot start [options] [--] NAME|IMAGE [COMMAND] [ARG...]
Start a container and invoke the command script within its root filesystem.
Command and arguments are passed to the script as input parameters.
In the absence of a command script and if a command was given, it will be executed directly.
Otherwise, an interactive shell will be started within the container.
Options:
-c, --conf CONFIG Specify a configuration script to run before the container starts
-e, --env KEY[=VAL] Export an environment variable inside the container
--rc SCRIPT Override the command script inside the container
-r, --root Ask to be remapped to root inside the container
-w, --rw Make the container root filesystem writable
-m, --mount FSTAB Perform a mount from the host inside the container (colon-separated)
—
Reply to this email directly, view it on GitHub<#216 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AL6M4OS6NPRD576GD7XQEL3Z6A44BAVCNFSM6AAAAABQ3CLR4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBVGY3DEOJZGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
It seems that enroot start will only use 1 GPU.
Could you let me know how I can make use of multiple GPU in the command ? I don’t see an option for that.
Thanks
Lucy
From: Lucy Zhang ***@***.***>
Date: Wednesday, October 30, 2024 at 10:30 AM
To: NVIDIA/enroot ***@***.***>, NVIDIA/enroot ***@***.***>
Cc: Author ***@***.***>
Subject: Re: [NVIDIA/enroot] enroot issue with installation inside (Issue #216)
Thank you very much. The suggestion works !
From: Felix Abecassis ***@***.***>
Date: Tuesday, October 29, 2024 at 7:02 PM
To: NVIDIA/enroot ***@***.***>
Cc: Lucy Zhang ***@***.***>, Author ***@***.***>
Subject: Re: [NVIDIA/enroot] enroot issue with installation inside (Issue #216)
Use the --rw argument:
$ enroot start --help
Usage: enroot start [options] [--] NAME|IMAGE [COMMAND] [ARG...]
Start a container and invoke the command script within its root filesystem.
Command and arguments are passed to the script as input parameters.
In the absence of a command script and if a command was given, it will be executed directly.
Otherwise, an interactive shell will be started within the container.
Options:
-c, --conf CONFIG Specify a configuration script to run before the container starts
-e, --env KEY[=VAL] Export an environment variable inside the container
--rc SCRIPT Override the command script inside the container
-r, --root Ask to be remapped to root inside the container
-w, --rw Make the container root filesystem writable
-m, --mount FSTAB Perform a mount from the host inside the container (colon-separated)
—
Reply to this email directly, view it on GitHub<#216 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AL6M4OS6NPRD576GD7XQEL3Z6A44BAVCNFSM6AAAAABQ3CLR4GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBVGY3DEOJZGM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After installing enroot in our dgx box, we tried starting the sqsh file.
enroot start -m /ads_ds3/data/eclair trtllm_2024022700.sqsh
We are able to get inside the container. Then we tried below installing and it failed with error of "read-only file system for my home directory".
Please advise.
luzhang@dc7nvdgxluna001:/ads_ds3/data/eclair$ pip install einops
WARNING: The directory '/home/luzhang/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
Defaulting to user installation because normal site-packages is not writeable
Collecting einops
Downloading einops-0.8.0-py3-none-any.whl (43 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 43.2/43.2 KB 3.5 MB/s eta 0:00:00
Installing collected packages: einops
ERROR: Could not install packages due to an OSError: [Errno 30] Read-only file system: '/home/luzhang/.local'
luzhang@dc7nvdgxluna001:/ads_ds3/data/eclair$ df -h /home
Filesystem Size Used Avail Use% Mounted on
fuse-overlayfs 1008G 128K 1008G 1% /
The text was updated successfully, but these errors were encountered: