You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd suggest to not set an entrypoint in the Dockerfile but leave that to the caller. The builder.sh script should be in the PATH so that one can run the docker container with docker run --rm prom/golang-builder:1.5.3-main builder.sh [options]. This will also allow to provide more than one command later, for diagnosis for example.
The text was updated successfully, but these errors were encountered:
Yes, that's what I'm using right now. I've found making the entrypoint always explicit helps the future reader of commands and is also more consistent than to sometimes set the --entrypoint and to sometimes rely on a default not immediately apparent.
I'd suggest to not set an entrypoint in the Dockerfile but leave that to the caller. The
builder.sh
script should be in thePATH
so that one can run the docker container withdocker run --rm prom/golang-builder:1.5.3-main builder.sh [options]
. This will also allow to provide more than one command later, for diagnosis for example.The text was updated successfully, but these errors were encountered: