Behavior of docker-compose up -d with version 2.32.0

midixinga · December 16, 2024, 10:35pm

Hi,

Did the behavior of “docker-compose up -d” change with Docker Compose version 2.32.0?

In the past only the containers with a new image were recreated and restartetd; now all containers are stopped and recreated and restarted?

thx

deanayalon · December 16, 2024, 11:04pm

It’s not just image change, it will restart any containers that had their configuration changed

midixinga · December 16, 2024, 11:47pm

There is no configuration change for the containers.
I found some minutes ago: It seems to be a Bug, solved in 2.32.1

github.com/docker/compose

[BUG] 2.32.0 unnecessarily recreates containers and loses volumes

opened 02:50AM - 14 Dec 24 UTC

closed 09:26AM - 16 Dec 24 UTC

sayhiben

kind/bug

### Description My team manages a Django application backed by MySQL. In the de…velopment environment, each service runs in a separate container orchestrated by Docker Compose on GitHub Codespaces using their Docker-in-Docker devcontainer feature. This devcontainer feature defaults to the latest version of Docker Compose when creating new Codespaces. As of this morning, we have been unable to persist data in MySQL's attached volume, and the container seems to restart and/or be recreated unnecessarily Unfortunately, I haven't yet had time to come up with a solid explanation or understanding of what's happening, so I don't have good repro steps. That said, the issue is severe enough for my org. that I wanted to report the problem here before I stopped work for the weekend Here's the MySQL Docker image we pull, where the database volume is defined: https://github.com/docker-library/mysql/blob/090eb25ac69bca920fc5320484bc35aac92a8143/8.0/Dockerfile.debian Our in-house reproduction steps have been to: 1. Get a shell_plus session in our Django app inside the container 2. Create instances of our models and save them 3. Exit the shell_plus session and container 4. Get another shell_plus session 5. Try to load the previously created instance from MySQL 6. Data miss After manually downgrading back to Docker Compose 2.31.0, I can no longer reproduce the data persistence issue and see fewer recreates/restarts when running `docker compose` commands. I apologize for the lack of specifics in this report, but again, given the instability, I figured that perhaps Docker Compose maintainers would want to hear from a canary sooner than later ### Steps To Reproduce I'm unsure how reproducible this is outside my specific set of Dockerfiles and Docker Compose configurations (which I am disallowed to share), but I'd test with using a MySQL 8 image based on `mysql:8-debian` and see if you can persist data in the volume it creates using Docker Compose 2.32.0. I will try to give this some time on Monday and post a minimal reproducible example if I find it ### Compose Version ```Text 2.32.0 ``` ### Docker Environment ```Text Client: Version: 27.3.1-1 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.19.2 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.32.0 Path: /usr/libexec/docker/cli-plugins/docker-compose Server: Containers: 11 Running: 11 Paused: 0 Stopped: 0 Images: 15 Server Version: 27.3.1-1 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: false userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: 88c3d9bc5b5a193f40b7c14fa996d23532d6f956 runc version: bc20cb4497af9af01bea4a8044f1678ffca2745c init version: de40ad0 Security Options: apparmor seccomp Profile: builtin cgroupns Kernel Version: 6.5.0-1025-azure Operating System: Ubuntu 20.04.6 LTS (containerized) OSType: linux Architecture: x86_64 CPUs: 16 Total Memory: 62.78GiB Name: codespaces-151e8e ID: 6745412a-81e5-4daa-b556-7bf87382b12b Docker Root Dir: /var/lib/docker Debug Mode: false Username: codespacesdev Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false ``` ### Anything else? - [docker-in-docker devcontainer feature](https://github.com/devcontainers/features/tree/main/src/docker-in-docker)

Topic		Replies	Views
[SOLVED] Docker compose up recreates every time General	3	3204	February 21, 2023
Mysterious result after Docker Update General aws , docker , docker-compose	0	660	September 16, 2021
Docker-Compose Theory General	2	800	April 6, 2018
Creation of new container when there is update in docker compose file General docker , docker-compose	1	10	January 10, 2025
Docker-compose up remove my existing conainer Compose	0	347	May 21, 2021

Behavior of docker-compose up -d with version 2.32.0

Related topics