One topic I'd like to see more discussion around is how best to set up staging environments for Docker Compose projects. Ever since the V2 migration, I've been

One topic I'd like to see more discussion around is how best to set up staging environments for Docker Compose projects. Ever since the V2 migration, I've been banging my head against multiple bugs in Docker Compose itself, which has severely damaged my trust in it as a production-ready utility. I no longer feel like I can safely update Compose without running extensive testing on each release. For example, my journey since migrating to V2 has been: * Originally on 1.29.2 - Stable and I did not encounter any issues. * Swapped to 2.3.3. - As part of the migration from V1, docker-compose lost track of several networks and started labeling them as external. Not a huge deal. - docker-compose stopped updating containers when the underlying image or configuration changed (#9291). This broke prod for a while until I noticed nothing was getting updated. * Updated to 2.7.0, which was the latest release at the time. - This introduced a subtle bug with env_file parsing (#9636), which again broke prod in subtle ways that took a while to figure out. * Updated to 2.8.0, which was the latest release at the time and before the warning was put up. * This broke a lot of things as it renamed containers and generated duplicate services, etc. * Finally swapped to 2.9.0. No issues yet, but I'm keeping an eye out.