Skip to content

"command" sets Entrypoint rather than Command? #8235

@larsks

Description

@larsks

I am running Kubernetes kubernetes-0.15.0 (git 0ea87e4) on RHEL 7.

I have a Dockerfile that contains:

ENTRYPOINT ["/usr/bin/stress"]

I would normally call it, for example, like this:

 docker run larsks/stress --cpu 1

I have a replicationController that contains:

      containers:
        - name: stress
          image: larsks/stress
          command: ["--cpu", "1"]

The resulting containers fail to start. When I inspect the
containers, I see:

"Config": {
    "Entrypoint": [
        "--cpu",
        "1"
    ],

That's wrong. The command: key should be setting the Command
field of the container, otherwise a variety of images that are
designed with a custom entrypoint will fail to run.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/apiIndicates an issue on api area.priority/awaiting-more-evidenceLowest 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.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions