Open f1amy opened 2 months ago
It seems I spent entire evening, night, and morning debugging this issue only to realize that I had enabled low power mode on my laptop 🤪
The issue generally seems to exist, just without cpu throttling it is much more bearable so I haven't paid attention earlier.
At this point I suggest anyone who is deploying applications the same way, rewrite setup script in a way that does not require up of constantly restarting containers (as they don't have dependencies at cold start).
There could could have been a change in docker engine in how it (less) tolerates restarting containers in up/down commands, so this is the case someone could take a look if that was desirable.
Description
Hello, I run a project with ~12 sets of Docker Compose applications, all connected by networks (databases, cache, webservers and php workers and applications), all have volumes and volume mounts for code or databases. I launch my project via
docker compose
withmake
files, firstly launching application services, then sequentially each application one by one.Recently, I did an update to Ubuntu 24.04 LTS, update WSL (wsl --update) on Windows 11. After the update, I could see that cold-starting the project takes extremely long time (20-30 minutes) compared to 1-3 minutes prior. The behavior is as follows: first containers from application services start pretty fast, then with each application set it takes them 20-30 seconds more to start, ending with over 170 seconds to start. The CPU usage seems to be the issue, but I could not find high cpu utilization processes with
top
when this happens.This makes developing the project impossible, because containers would crash and restart before its required dependencies could be installed for setup (this used to work perfectly) / up container, exec into it, install dependencies/warm cache.
Reproduce
Expected behavior
Containers should start fast enough (to hit application error).
docker version
docker info
Diagnostics ID
5F033B04-356E-4708-9131-A4943D70ED24/20240908045633
Additional Info
Could not get to generate diagnostics ID from target machine (v4.33.1), but the issue seems to be reproducible on other with similar environment.