Skip to content
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

Cannot use ENTRYPOINT in Dockerfile/docker-compose.yml #27

Open
iamamutt opened this issue Aug 18, 2021 · 1 comment
Open

Cannot use ENTRYPOINT in Dockerfile/docker-compose.yml #27

iamamutt opened this issue Aug 18, 2021 · 1 comment

Comments

@iamamutt
Copy link

Request to be able to use ENTRYPOINT w/ CMD like so:

ENTRYPOINT ["conda", "run", "-n", "my_custom_env", "my_script.py"]
CMD: ["--opt1", "val1", "--opt2", "val2"]

instead of:

CMD: ["conda", "run", "-n", "my_custom_env", "my_script.py", "--opt1", "val1", "--opt2", "val2"]

This would require moving entrypoint.sh functionality elsewhere in the Dockerfile, though.

@guzman-raphael guzman-raphael self-assigned this Sep 16, 2021
@guzman-raphael
Copy link
Collaborator

This will likely be a bit more involved. Adding some notes below after investigating it a bit further...

Likely need to make a distinction between:

  • Boot steps
  • Shell (interactive, nologin) steps (runs on normal bash shell)
  • Shell (interactive, login) steps (runs bash login like ssh, su)
  • Shell (non-interactive) steps (runs on every bash script invocation e.g. BASH_ENV and ENV env vars)

Bash script sourcing order for various shell modes: https://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html
Dash script sourcing order for various shell modes: https://linux.die.net/man/1/dash

@guzman-raphael guzman-raphael removed their assignment Sep 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants