Why doesn't the container start?

Question

My docker-compose file is simple:

npm:
    image: node
    volumes:
        - C:\Users\Samir\npm\:/home/dev
    container_name: npm

When I run it:

docker-compose up -d

I get:

Starting npm

Then, nothing happens:

docker ps
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

Any idea?

Erik Dannenberg · Accepted Answer · 2016-04-18 15:01:16Z

1

Per default the Node image is designed for interactive use and simply starts a Node REPL. When you run docker-compose up -d the Node REPL will start and exit immediately as no interactive terminal is availabe. Try:

docker-compose run -it npm

Note that this is currently not supported on Windows, you will need to use docker run -it -v ... node instead.

If you want to start your application instead simply override the default command in your docker-compose.yml

answered Apr 18, 2016 at 15:01

Erik Dannenberg

6,1362 gold badges19 silver badges24 bronze badges

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

Collectives™ on Stack Overflow

Why doesn't the container start?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related