Should I run plain Docker Compose in production in 2026? (distr.sh)

Article summary

The article discusses the use of plain Docker Compose in production environments in 2026, highlighting its limitations and potential operational gaps. It provides solutions to common issues such as orphan containers, disk space management, and security risks. The author also introduces Distr, a platform that helps software companies distribute their applications to self-managed environments. The article concludes that while Docker Compose can still be used in production, it requires careful handling of its operational gaps.

Main themes

• Docker Compose in production
• Container orchestration
• Podman vs Docker
• Systemd integration
• Container security
• Deployment management

What commenters say

• Using Podman with systemd can provide better management of containers as services.
• Podman Compose is not a reliable replacement for Docker Compose due to its limitations and instability.
• Systemd is a versatile tool that can handle various system tasks, including container management, but its complexity can be a drawback.
• The choice between Docker and Podman depends on specific use cases and requirements, with some preferring Podman's daemonless architecture.
• Docker Compose has quirks and limitations, such as issues with gvisor and internal networks, that may vary in severity depending on the use case.
• The use of Podman with Docker Compose can lead to subtle differences in behavior and potential conflicts, making it important to carefully evaluate the trade-offs.
• Some argue that systemd's modular components can be beneficial, while others see it as an overloaded kitchen sink that adds unnecessary complexity.
• The integration of Podman with systemd can provide benefits, but it may also introduce new challenges and require careful consideration of the system's overall architecture.