Docker container not starting

Docker Desktop
1

Hello,

For 2 years I m using docker desktop for windows. I only run 1 container and have no other docker experience or knowledge.
Now the windows machine installed updates and rebooted . After the reboot Docker desktop version 3.6 was not starting anymore. I removed it and installed the latest version 4.0.1 that is starting.

I always started my container with docker-compose up

When I try to do this now I get the error :

no such service: _invoiceplane_1

This is my docker-compose.yml file :

version: '2'

services:
  mysql:
    restart: always
    image: sameersbn/mysql:5.7.24
    environment:
    - DB_USER=invoiceplane
    - DB_PASS=password
    - DB_NAME=invoiceplane_db
    volumes:
    - D:\INVOICEPLANE\mysql:/var/lib/mysql

  invoiceplane:
    restart: always
    image: sameersbn/invoiceplane:1.5.9-2
    command: app:invoiceplane
    environment:
    - DEBUG=false
    - TZ=Asia/Kolkata

    - DB_TYPE=mysqli
    - DB_HOST=mysql
    - DB_USER=invoiceplane
    - DB_PASS=password
    - DB_NAME=invoiceplane_db

    - INVOICEPLANE_URL=http://10.0.0.113:10080
    - INVOICEPLANE_PROXY_IPS=
    - INVOICEPLANE_BACKUPS_EXPIRY=0
    depends_on:
    - mysql
    volumes:
    - D:\INVOICEPLANE\invoiceplane:/var/lib/invoiceplane

  nginx:
    restart: always
    image: sameersbn/invoiceplane:1.5.9-2
    command: app:nginx
    environment:
    - INVOICEPLANE_PHP_FPM_HOST=invoiceplane
    - INVOICEPLANE_PHP_FPM_PORT=9000
    depends_on:
    - invoiceplane
    ports:
    - "10080:80"
    volumes_from:
    - invoiceplane

I used this docker file and instructions to do the initial setup :

https://hub.docker.com/r/sameersbn/invoiceplane

Can somebody help me to get my container running again without losing my data.?

Thanks,

Karel

2

I am having this same issue. Looks like it occurred with the 4.0 update. I am using Docker Desktop on the mac.

Docker Desktop: 4.0.1 (68347)
Docker: Docker version 20.10.8, build 3967b7d
Docker Compose: Docker Compose version v2.0.0-rc.3

For me, I was able to get around this by starting the containers one at a time like so. Try this:

docker-compose up -d mysql
docker-compose up -d invoiceplane
docker-compose up -d nginx

Somewhat defeats the purpose of having them bundled together in a compose file though.

3

FWIW: It looks like it might be due to the volumes_from directive in your nginx proxy. I have a similar configuration and I am unable to start the nginx container when the volumes_from field is set to one of my other containers. This is where the “no such service” seems to be coming from.

Changing the volume configuration to map a named volume did the trick. Reference: Compose file version 3 reference | Docker Documentation