[Bug] Docker Container keep restarting.

[shubham-cmyk]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

Docker container keep restarting.
👀 Ubuntu Local host

👀 AWS

What you expected to happen

👀 Docker Container logs

Container are not starting up in proper order.

How to reproduce

Release Version : 0.10.1

Follow up the general installation method as stated in Readme

Anything else

We are using v3 docker-compose which has removed ability of container for wait for eachother.

Version

v0.10.1

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[keon94]

The ordering is technically fine (depends_on field in the compose file manages the ordering). The problem is, each container has a bootstrap process that takes some time to complete (e.g. mysql), so just because it has started it doesn't mean it's ready. In this case devlake is trying to talk to mysql before it is fully ready, and that throws an error.

With docker-compose v2 one would define healthchecks in the compose file and have the containers wait using conditions until their dependencies are healthy before boostrapping. v3 removed this feature as far as I am aware.

So our options are:

1. Use the v2 docker-compose spec, and use healthchecks and conditions in the compose file
2. Enhance the devlake service logic to retry DB connectivity for a while
3. Apparently the more recent compose versions allow backwards portability as far as support for conditions go see this discussion. Maybe investigate this and see if it'll work.

[hezyin]

@shubham-cmyk Hi Shubham, it's normal for the DevLake container to restart a couple of times while waiting for the MySQL container to boot up, but usually, it wouldn't take longer than 15 seconds. If you see the DevLake container constantly restarting while the MySQL container is up and running, then there's something wrong with the connection between the DevLake container and the MySQL container. I'd suggest that you double-check the connection string in the .env file. Make sure you use mysql:3306 instead of localhost:3306 in the connection string. Let me know if the problem persists. Thanks!