-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: Arguments to the Entrypoint #4208
Comments
Try |
It worked. Thanks. |
ndeloof
pushed a commit
to ndeloof/compose
that referenced
this issue
Jan 30, 2023
ndeloof
pushed a commit
to ndeloof/compose
that referenced
this issue
Jan 30, 2023
ndeloof
pushed a commit
to ndeloof/compose
that referenced
this issue
Jan 31, 2023
ndeloof
pushed a commit
to ndeloof/compose
that referenced
this issue
Feb 1, 2023
ndeloof
pushed a commit
that referenced
this issue
Feb 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my compose file I have:
my_server:
image: yashgt/proc1:latest
command: "2"
docker-compose up treats the command as the executable. I get an error that says:
ERROR: for my_server Cannot start service my_server: oci runtime error: container_linux.go:247: starting container process caused "exec: "2": executable file not found in $PATH"
There should be a way to retain the entrypoint defined in the dockerfile and only pass a runtime argument to it from the compose file.
The text was updated successfully, but these errors were encountered: