taiga-docker icon indicating copy to clipboard operation
taiga-docker copied to clipboard

docker-compose

Open mshanak opened this issue 3 years ago • 1 comments

I tried to run docker-compose on mac, during the process of running I get the following error:

Note: I found that docker created a folder called taiga.conf instead of a file. when I created it manually the process finished successfully but I cannot access the taiga website.

Creating tiga-docker_taiga-protected_1       ... done
Creating tiga-docker_taiga-db_1              ... done
Creating tiga-docker_taiga-front_1           ... done
Creating tiga-docker_taiga-events-rabbitmq_1 ... done
Creating tiga-docker_taiga-async-rabbitmq_1  ... done
Creating tiga-docker_taiga-events_1          ... done
Creating tiga-docker_taiga-back_1            ... done
Creating tiga-docker_taiga-gateway_1         ... error
Creating tiga-docker_taiga-async_1           ... done

ERROR: for tiga-docker_taiga-gateway_1  Cannot start service taiga-gateway: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: rootfs_linux.go:60: mounting "/Users/mahdi/Downloads/tiga-docker/taiga-gateway/taiga.conf" to rootfs at "/var/lib/docker/overlay2/cf63889c35f741bd9f1f0876ff183a9aebdafaa2f53f83773b83ab6e38446657/merged/etc/nginx/conf.d/default.conf" caused: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for taiga-gateway  Cannot start service taiga-gateway: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: rootfs_linux.go:60: mounting "/Users/mahdi/Downloads/tiga-docker/taiga-gateway/taiga.conf" to rootfs at "/var/lib/docker/overlay2/cf63889c35f741bd9f1f0876ff183a9aebdafaa2f53f83773b83ab6e38446657/merged/etc/nginx/conf.d/default.conf" caused: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.
Mahdis-MacBook-Pro:tiga-docker mahdi$ docker-compose up
Docker Compose is now in the Docker CLI, try `docker compose up`

tiga-docker_taiga-protected_1 is up-to-date
tiga-docker_taiga-events-rabbitmq_1 is up-to-date
tiga-docker_taiga-async-rabbitmq_1 is up-to-date
tiga-docker_taiga-db_1 is up-to-date
tiga-docker_taiga-front_1 is up-to-date
tiga-docker_taiga-events_1 is up-to-date
tiga-docker_taiga-back_1 is up-to-date
tiga-docker_taiga-async_1 is up-to-date
Starting tiga-docker_taiga-gateway_1 ... error

ERROR: for tiga-docker_taiga-gateway_1  Cannot start service taiga-gateway: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: rootfs_linux.go:60: mounting "tiga-docker/taiga-gateway/taiga.conf" to rootfs at "/var/lib/docker/overlay2/cf63889c35f741bd9f1f0876ff183a9aebdafaa2f53f83773b83ab6e38446657/merged/etc/nginx/conf.d/default.conf" caused: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type

ERROR: for taiga-gateway  Cannot start service taiga-gateway: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: rootfs_linux.go:60: mounting "tiga-docker/taiga-gateway/taiga.conf" to rootfs at "/var/lib/docker/overlay2/cf63889c35f741bd9f1f0876ff183a9aebdafaa2f53f83773b83ab6e38446657/merged/etc/nginx/conf.d/default.conf" caused: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
ERROR: Encountered errors while bringing up the project.

mshanak avatar Apr 28 '21 08:04 mshanak

+1

bolgovrussia avatar Apr 29 '22 18:04 bolgovrussia

I solved it out..

if your postgres volume already has data in it, (from a different install attempt) then it won't initialize properly. https://github.com/docker-library/postgres/issues/773#issuecomment-710144766

I checked that by finding the postgres container and logging into the container... and looking at the contents of this directory... /var/lib/postgresql/data and found a bunch of stuff... See: https://www.ibm.com/docs/en/workload-automation/9.5.0?topic=compose-accessing-docker-containers

from docker-compose.yml: volumes: - taiga-db-data:/var/lib/postgresql/data

In order to re-initialize postgres with the user and password specified, I cleared out the containers AND any volumes. https://stackoverflow.com/a/58573823

You can clear that out with this...
docker-compose down --rmi all --volumes

Then trying again. That fixed my issue.

Mbd06b avatar May 12 '22 01:05 Mbd06b

+1

oussjarrousse avatar Oct 28 '22 17:10 oussjarrousse