stable containers don't work if downed once

Description:

When setting up the dev environment, the first launch of a stable container works perfectly. However, doing docker compose down stableXX and then docker compose up -d stableXX, there will be an error where the container says the server is not installed, it will try to install it and fail.

Steps to reproduce

Initial setup

git clone https://github.com/juliusknorr/nextcloud-docker-dev
cd nextcloud-docker-dev
./bootstrap.sh

cd workspace/server
git fetch origin stable31:stable31
git worktree add ../stable31 stable31
cd ../stable31
git submodule update --init

docker compose up -d nextcloud stable31

At this point, both nextcloud and stable31 works.

The breaking point

docker compose down
docker compose up -d nextcloud stable31

nextcloud.local works but stable31.local doesn't

You unfortunately have to remove the volumes to be able to relaunch the stable containers.

Reproduce the failure using bootstrap.sh, the stable31 worktree, and the docker compose up/down commands described in the issue. Inspect the compose configuration and volume behavior for stable31; done means a stable container starts successfully after docker compose down and docker compose up without removing volumes.