docker-compose up Error

[aadeshkulkarni]

Description:

docker-compose up returns the following errors:

1. Mounts denied error for the db host volume address. (for Mac specifically) ( Screenshot attached below )
   (Which when resolved by changing the host address, returns the next error)

2. Error P1001: Can't reach database server.
   The cms-app docker container runs the migration script even before the cms-db docker container is up. (Error Screenshot attached below)

Details on Issue 2:

By default, Docker Compose only ensures that the services listed under the depends_on property are started before the dependent service. This means that Compose doesn't guarantee that these services are fully operational and ready to process requests, but only that their containers are running.

It is however possible to set conditions to define when one service should start or wait for another service to reach a specific state. These conditions are defined in the condition property and take three possible values: service_started, service_healthy, and service_completed_successfully.

Proposed Solution:

1. Investigate and resolve the issue with the Host volume address to ensure the build mount is successful.
2. Set the appropriate conditions for the cms-app container to wait for the cms-db container to reach a specific state before running the migration script.

Steps to Reproduce the issue

1. Run the docker-compose up command on a local machine.
2. Monitor the logs and observe the build mount failure and premature migration script execution.
3. Review the Docker Compose file for the services' dependencies and conditions.
4. Implement the necessary changes to resolve the issues.

Additional resources

https://www.warp.dev/terminus/docker-compose-depends-on

Proposed solution

https://github.com/peter-evans/docker-compose-healthcheck

Screenshots

Issue 1 (Mount fail)

Issue 2 (container cms-app starting before starting cms-db service is healthy)

[geekyharsh05]

@aadeshkulkarni you can configure the file sharing by going to settings. it works for me.

[aadeshkulkarni]

@aadeshkulkarni you can configure the file sharing by going to settings. it works for me.

I have tried doing this. But Docker does not let me create a directory for that address. (Using MacOS)
There is a probability that something must be wrong on my end here, debugging rn.

There was one more individual who was facing this issue in discord
Message link - https://discord.com/channels/1171768226691162162/1178318174920380566/1216292791911714938

[devsargam]

hey @aadeshkulkarni, I am the author of Dockerfile for this repo.
Try @geekyharsh05 approach or change the postgres volume in docker-compose.yml

TY

[devsargam]

Also, @aadeshkulkarni this has been resolved.

It's just the way docker is wired in mac os.

[aadeshkulkarni]

Configuring the file sharing by going to settings didn't work for me.

I have changed the postgres volume to make it work for now.

Can you confirm if Issue#2 is reproducible ? @devsargam & @geekyharsh05
This issue only occurs during initial app setup (for fresh first time db migrations)
If you've already performed db migrations, you might need to clear your volumes to test this.

[devsargam]

@aadeshkulkarni haven't reproduced but your point seems valid.

[geekyharsh05]

@devsargam what if you try this approach, instead of using absolute path we can use relative path, so it'll become easy for anyone to setup the project using docker. Is it a right approach?

volumes:
      - ./postgres-data:/var/lib/postgresql/data

[aadeshkulkarni]

@devsargam what if you try this approach, instead of using absolute path we can use relative path, so it'll become easy for anyone to setup the project using docker. Is it a right approach?

volumes:
      - ./postgres-data:/var/lib/postgresql/data

This PR #182 has the solution @geekyharsh05 mentioned above for issue #1.

It also has issue #2 resolution. but keeping the PR as draft until #2 is reproducible by someone else.

Edit:
Issue#2 is reproducible:
Discord > os-doubts-and-discussions:

[devsargam]

Just in case did you do
docker rmi
docker compose up --build?

[aadeshkulkarni]

Yes,

removed db volume on the local host by deleting the/postgres-data directory. (to clear all previous db migrations)

Then docker compose up with or without --build should trigger the issue