Hey there, I’ve been running into a weird issue with databases corrupting and I seem to have tracked it down to one main issue: Apparently the docker-compose.yml files that I have included aren’t stopped when I run docker compose stop on the main docker-compose.yml. Any idea why that is? Some cont…

Please share the output of docker compose config so we can see the full rendered config. Make sure to anonymize public ips, domain names and secrets, but leave the rest untouched. Without having any context information, I would assume it’s related to the grace period when containers are stopped. A…

[image] meyay: grace period It’s definitely not the grace period. If I enter the directory with the second docker-compose.yml file and run docker compose stop there the containers in question immediately stop just as expected. The corruption seems to stem from the fact that something is stop…

It is highly unlikely that your problem is not related to the process inside the container being killed by SIGKILL, otherwise it would terminate gracefully without data corruption. So either the process inside the container requires a different signal than SIGTERM to initiate the graceful terminati…

[image] meyay: It is highly unlikely that your problem is not related to the process inside the container being killed by SIGKILL I’m pretty sure it is. I checked the logs (by attaching! to the containers), and immediately after I start the stopping process I get some weird corruption errors…

The first idea is to get a clear problem description. You write about corrupt database, it seems your compose is using a default postgres image. Does the postgres log tell you it is shut down hard or needs to recover upon start? Are the bind mounts local folders or on a remote share?

First off: all the mounts are bind mounts, nothing remote. previously I wasn’t really willing to kill my containers again so I wanted to avoid triggering this again, but figuring it would help with the resolution I just did exactly that. Having changed absolutely nothing, my included containers di…

This is the log of both shutdown and startup of postgres?

yes. That’s the script running docker compose stop and then docker compose start

It’s really strange, haven’t seen that before. Did you check your disk for corruption? Usually Postgres is very stable. You could try to isolate and run fewer services. Sorry, you probably won’t get around some more testing.

Docker compose stop doesn't stop included containers

General

ultrablack (Ultrablack) July 14, 2024, 7:38pm 6

any updates on this? I don’t think that’s intended behaviour…

Topic		Replies	Views
Docker Compose shows error when stopping Docker Desktop	5	2564	October 31, 2016
Docker compose stop multiple containers Compose	2	1805	August 3, 2023
One of the postgres containers stops as soon as it starts General docker	4	20191	August 22, 2022
Included file does not re-up after updates Compose docker-compose , linux	6	182	January 6, 2026
Container exits if invoked from compose Compose	0	1001	October 26, 2016

Docker compose stop doesn't stop included containers

Related topics