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
Don't use deno as entrypoint #57
Comments
Thanks for opening an issue / bringing this up! Could you explain the benefit? What is it solving? How would this change the usage? (How do you call bash in the node image?) Why doesn't --entrypoint suffice? Why does it break gitlab? This was suggested and introduced by @Minigugus in #23. Would be interested to hear their counter. I'm not adverse to this change, but I did think it was neat... But I just want to understand more fully. |
@DanielRamosAcosta Oh nice 😮 Pretty cool to bypass @hayd Currently, |
@DanielRamosAcosta Happy to take PR! |
One annoying part of this is that |
It's possible to hard-code Deno commands in |
Give me some time, I'll try to prepare a PR during this week 😄 , thanks you all @Minigugus @hayd |
something like this? #!/bin/bash
set -e
# how to test if $1 is in (run, cache, bundle, completions, eval, fmt, lint, repl, test, types) ?
if [ "$1" = 'run' ]; then
exec gosu deno "$@"
fi
exec "$@" https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#entrypoint |
#!/bin/bash
set -e
case "$1" in
run | \
cache | \
bundle | \
completions | \
eval | \
fmt | \
lint | \
repl | \
test | \
types) \
exec gosu deno "$@";;
esac
exec "$@" |
I think it should be a
docker-entrypoint.sh
file, like node does.This would allow using the image for launching other kind of scripts, and allowing Gitlab CI to work, for example.
I cant PR if you want. Cheers!
The text was updated successfully, but these errors were encountered: