What is the issue?
When using Dagger to run a container with a vim ENTRYPOINT, the expected behavior of launching the interactive vim editor does not occur. Instead, the shell opens without triggering vim, despite the ENTRYPOINT being defined in the Dockerfile.
Dagger version
dagger v0.18.9 (docker-image://registry.dagger.io/engine:v0.18.9) darwin/amd64
Steps to reproduce
- Dockerfile
FROM alpine
RUN apk add --no-cache vim
ENTRYPOINT ["vim"]
- Dagger Interactive Shell`
- In Shell: Build Container
✔ container | build . | terminal
● Attaching terminal:
container: Container!
.build(
│ │ context: Host.directory(path: "~/project/vim"): Directory!
│ ): Container!
- Observation
Dagger shell opens as:
5 If the check entrypoint, it is displayed
✔ container | build . | entrypoint 0.4s
vim
However, the entrypoint is not triggered as expected. You need to manually run Vim, even though it’s set as the ENTRYPOINT.
Log output
Logs in the reproduce section
What is the issue?
When using Dagger to run a container with a vim ENTRYPOINT, the expected behavior of launching the interactive vim editor does not occur. Instead, the shell opens without triggering vim, despite the ENTRYPOINT being defined in the Dockerfile.
Dagger version
dagger v0.18.9 (docker-image://registry.dagger.io/engine:v0.18.9) darwin/amd64
Steps to reproduce
Dagger shell opens as:
5 If the check entrypoint, it is displayed
However, the entrypoint is not triggered as expected. You need to manually run Vim, even though it’s set as the ENTRYPOINT.
Log output
Logs in the reproduce section