can enroot overwrite entrypoint of docker image just like how docker run works.

Open
#266 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
50/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker, shell
Domain
cli

Research direction

Start by examining the enroot start command and its handling of the command after the container name, then compare that behavior with Docker's --entrypoint option. Reproduce the vllm image example and verify that an enroot invocation can launch bash instead of the image's default vllm serve entrypoint.

Written by the indexing model from the issue text.

Description

as we know, official vllm docker image's entrypoint is 'vllm serve',
and in docker environment we can use --entrypoint option to overwrite the default entrypoint like this:
docker run --entrypoint /bin/bash vllm/vllm-openai:v0.18.0

when I use same image in enroot environment, seems this is no way to overwrite it.
enroot create --name vllm-testagent vllm-openai-v0.18.0.sqsh
enroot start --root --rw vllm-testagent bash -c "echo hello"

a workaround is build another image use docker file like:
FROM vllm/vllm-openai:v0.18.0
ENTRYPOINT []
CMD ["/bin/bash"]
WORKDIR /root

is that possible to overwrite default entrypoint in enroot environment? thanks.

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.