Issue with docker compose: container command not found

Question

I'm having an issue when trying to start multiple containers with docker-compose:

Dockerfile:

FROM nginx:1.9
ADD ./nginx-sites/default /etc/nginx/sites-available/default

docker-compose.yml:

version: "2"
services:
  web:
    build: .
    ports:
      - "80:80"
    volumes:
      - ./src:/var/www
    links:
      - fpm
  fpm:
    image: php:7-fpm
    volumes:
      - ./src:/var/www

When I use docker-compose up to start the application, I get the following error:

ERROR: Container command not found or does not exist.

Would love some help with this issue.

I just started looking at this as I had the same problem. If you remove the volumes section from your fpm service does it start up? (obviously without the files accessible to php-fpm, but just for interests sake) — TomLingham
– TomLingham, Commented Feb 14, 2016 at 5:28
yeah. without the volumes section under fpm, it starts up normally. — dev_mrsb
– dev_mrsb, Commented Feb 14, 2016 at 5:55
actually if i set the volumes as "./src:/var/www/html" (for both web and fpm services), the application starts, but I'm not able to access anything over localhost. — dev_mrsb
– dev_mrsb, Commented Feb 14, 2016 at 6:14
Might need to hit the IP of the boot2docker vm rather than 'localhost' if you are on Mac or Windows. Mine's set to 192.168.99.100 by default. — TomLingham
– TomLingham, Commented Feb 14, 2016 at 6:23
Yup, that was it. Thanks a lot. I'm still not sure why the volume needs to be /var/ww/html, but it may be because of php-fpm. If you'll post an answer, I can mark it as accepted. — dev_mrsb
– dev_mrsb, Commented Feb 14, 2016 at 6:30

Alexander Blunck · Accepted Answer · 2016-02-24 13:08:26Z

12

Like mentioned in the comments to the original question the php:fpm image requires for it's volume to be set to /var/www/html.

If you want to use a different dir you can work around that by using your own Dockerfile (based on php:fpm). That Dockerfile would like this:

FROM php:fpm

WORKDIR /var/www

It seems like setting the workdir to the desired dir does the trick.

Then in your docker-compose.yml you would build with that Dockerfile instead of using the php:fpm image directly.

version: "2"
services:
  # ...
  fpm:
    build: ./path/to/dockerfile
    volumes:
      - ./src:/var/www

answered Feb 24, 2016 at 13:08

Alexander Blunck

1,22313 silver badges17 bronze badges

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

1 Comment

uptownhr Over a year ago

This should be the correct answer! The current marked answer is bogus.

Collectives™ on Stack Overflow

Issue with docker compose: container command not found

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related