-
Notifications
You must be signed in to change notification settings - Fork 42.8k
"command" sets Entrypoint rather than Command? #8235
Copy link
Copy link
Closed
Labels
area/apiIndicates an issue on api area.Indicates an issue on api area.priority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.Lowest priority. Possibly useful, but not yet enough support to actually get it done.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.Categorizes an issue or PR as relevant to SIG API Machinery.
Metadata
Metadata
Assignees
Labels
area/apiIndicates an issue on api area.Indicates an issue on api area.priority/awaiting-more-evidenceLowest priority. Possibly useful, but not yet enough support to actually get it done.Lowest priority. Possibly useful, but not yet enough support to actually get it done.sig/api-machineryCategorizes an issue or PR as relevant to SIG API Machinery.Categorizes an issue or PR as relevant to SIG API Machinery.
I am running Kubernetes kubernetes-0.15.0 (git 0ea87e4) on RHEL 7.
I have a Dockerfile that contains:
I would normally call it, for example, like this:
I have a replicationController that contains:
The resulting containers fail to start. When I inspect the
containers, I see:
That's wrong. The
command:key should be setting theCommandfield of the container, otherwise a variety of images that are
designed with a custom entrypoint will fail to run.