-
Notifications
You must be signed in to change notification settings - Fork 693
Not possible to pass arguments when doing docker run #1448
Comments
I'm not sure either why this is happening. I would suggest building an image tarball and post the image config JSON (which contains the entrypoint setting) and ask docker forums on the reason behind this behavior. Do keep us posted. |
So we had a look at the config JSON and we saw that the entrypoint from the bazel build was:
When comparing this to the Dockerfile version it was:
We then changed from:
to:
We then looked in the config JSON and saw that the entrypoint now was:
When we then ran
Seems like the behaviour of using |
Seems like behavior is because of the _validate_command function and this transformation is done for both the |
This issue has been automatically marked as stale because it has not had any activity for 180 days. It will be closed if no further activity occurs in 30 days. |
This issue was automatically closed because it went 30 days without a reply since it was labeled "Can Close?" |
We're building an image like this:
BUILD
:entrypoint.sh
:When running this locally with
docker run bazel/task-images/bigquery:docker --help
we see that the arguments are not passed to the entrypoint script:If skip instead run by specifying the entrypoint like
docker run --entrypoint /app/entrypoint.sh bazel/task-images/bigquery:docker --help
we see that the arguments are passed:Not sure if this is an intended behaviour or not (and also not sure it should go here), but could not find any info when looking around.
The text was updated successfully, but these errors were encountered: