Docker-compose fails with error "No command specified"

Question

Starting the container with the run command

docker run -it -d -p 8888:8888 install_advisor node src/server

works as expected. But trying to bring it up using docker-compose results in the error:

"ERROR: for advisor Cannot create container for service advisor: No command specified"

What am I doing wrong?

Contents of docker-compose.yml

advisor:
  build:
    context: .
    dockerfile: DockerfileAdvisor
  ports:
    - "8888:8888"
  restart: always
  privileged: true

Contents of DockerfileAdvisor

FROM XYZ
ENTRYPOINT [ "node", "src/server" ]

ronkot · Accepted Answer · 2016-11-24 06:49:38Z

2

I'm a bit surprised that your solution doesn't work as it is. But you can probably fix it in several ways. Here some suggestions:

1) Change your DockerFileAdvisor file to

FROM XYZ
COMMAND [ "node", "src/server" ]

2) If DockerFileAdvisor really contains just the two rows that are shown in your question, you don't even need it. Just specify image: XYZ and command: [ "node", "src/server" ] in your docker-compose.yml:

advisor:
    image: XYZ
    ports:
      - "8888:8888"
    restart: always
    privileged: true
    command: [ "node", "src/server" ]

Maybe you'd like to take a look on Docker documentation how ENTRYPOINT and COMMAND directives play together. In short, with ENTRYPOINT you can make an image to look like an executable and use COMMAND to just pass parameters for it.

answered Nov 24, 2016 at 6:49

ronkot

6,4674 gold badges31 silver badges43 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

ronkot Over a year ago

Great, nice to hear it! :)

Collectives™ on Stack Overflow

Docker-compose fails with error "No command specified"

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related