[GH-ISSUE #1502] 🐛 [Bug] Difficulty stopping containers in docker-compose.dev.yaml #672

New issue

Closed

opened 2026-02-25 21:35:38 +03:00 by kerem · 0 comments

kerem commented

2026-02-25 21:35:38 +03:00

Owner

Originally created by @Revisto on GitHub (May 1, 2025).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/1502

🐛 Bug

When running the development environment using docker-compose -f docker-compose.dev.yaml up, it's sometimes impossible to stop the running containers using docker compose down or Ctrl+C. The command hangs indefinitely, requiring a full Docker service restart (sudo systemctl stop docker.socket docker.service) and manual killing of container processes to resolve.

Screenshots

Possible Solution
Based on local testing, adding stop_grace_period: 30s (or a similar reasonable value like 1m) to the services in docker-compose.dev.yaml seems to resolve this issue, allowing the containers to stop gracefully.

Version & Environment

Rev: [42933b85d7]

OS: [Ubuntu 25.04]

Originally created by @Revisto on GitHub (May 1, 2025). Original GitHub issue: https://github.com/cypht-org/cypht/issues/1502  ## 🐛 Bug When running the development environment using `docker-compose -f docker-compose.dev.yaml up`, it's sometimes impossible to stop the running containers using `docker compose down` or `Ctrl+C`. The command hangs indefinitely, requiring a full Docker service restart (`sudo systemctl stop docker.socket docker.service`) and manual killing of container processes to resolve. **Screenshots** ![Image](https://github.com/user-attachments/assets/3dda6769-f1a6-494d-9a0d-006aee8bc167) **Possible Solution** Based on local testing, adding `stop_grace_period: 30s` (or a similar reasonable value like `1m`) to the services in `docker-compose.dev.yaml` seems to resolve this issue, allowing the containers to stop gracefully. ### Version & Environment  Rev: [42933b85d7f36b1a7841210dcaac4af8d86acdbe]  OS: [Ubuntu 25.04]