We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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"]
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.
entrypoint.sh
The text was updated successfully, but these errors were encountered:
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:
BASH_ENV
ENV
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
Sorry, something went wrong.
No branches or pull requests
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.The text was updated successfully, but these errors were encountered: