Starting AIO with docker-compose breaks mastercontainer update

[shalak]

Steps to reproduce

1. Start nextcloud-aio something like the following compose (most likely you may need to pull some old nextcloud/all-in-one image beforehand):

services:
  caddy:
    image: caddy:alpine
    restart: unless-stopped
    container_name: caddy
    volumes:
      - /srv/fast/caddy/Caddyfile:/etc/caddy/Caddyfile
      - /srv/fast/caddy/certs:/certs
      - /srv/fast/caddy/config:/config
      - /srv/fast/caddy/data:/data
      - /srv/fast/caddy/sites:/srv
      - /mnt/ssl:/mnt/ssl
    network_mode: "host"

  nextcloud:
    image: nextcloud/all-in-one:latest
    restart: unless-stopped
    container_name: nextcloud-aio-mastercontainer
    ports:
      - "8080:8080"
    environment:
      - APACHE_PORT=11000
      - NEXTCLOUD_DATADIR=/srv/fast/ncdata
      - NEXTCLOUD_MEMORY_LIMIT=2048M
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
    depends_on:
      - caddy

volumes:
  nextcloud_aio_mastercontainer:

2. Try to update

Expected behavior

mastercointainer is able to handle this situation and updates without problems

Actual behavior

mastercontainer fails to update, because the volume is not named nextcloud_aio_mastercontainer - that's because docker-compose will prepend the name with project name, which usually is the directory name in which the docker-compose.yaml is located, e.g. mydir_nextcloud_aio_mastercontainer, thus resulting in following error showing in mastercontainer logs:

It seems like you did not give the mastercontainer volume the correct name? (The 'nextcloud_aio_mastercontainer' volume was not found.)

Either the mastercontainer should inspect the volume that is mounted to it, be it automatically or via env variable, OR it should be clearly stated in docs, to use:

volumes:
  nextcloud_aio_mastercontainer:
    external: true

and run docker volume create --name nextcloud_aio_mastercontainer before docker compose up -d.

Host OS

Doesn't matter

Nextcloud AIO version

This happened to me when I updated to Nextcloud AIO v4.6.2, I assume from v4.5.0

Current channel

latest

Other valuable info

[shalak]

How to fix the installation:

docker volume create --name nextcloud_aio_mastercontainer
docker run --rm -it -v PROJECT_NAME_nextcloud_aio_mastercontainer:/from -v nextcloud_aio_mastercontainer:/to alpine ash -c "cd /from ; cp -av . /to"

(replace PROJECT_NAME_nextcloud_aio_mastercontainer with the name of the volume that compose created for you the first time, you can double-check it via docker inspect nextcloud-aio-mastercontainer)

Then, edit the compose file, add the external: true to the volume and bring the compose up.

After confirming that everything works, I guess best is to remove the now dangling volume:
First, while nextcloud is healthy, confirm that the old volume is dangling:

docker volume ls -q -f dangling=true

Then:

docker volume rm PROJECT_NAME_nextcloud_aio_mastercontainer

[shalak]

The weirdest part is that I did couple of mastercontainer updates since February (when I started my journey with nextcloud), and only now this became a problem.

[Zoey2936]

this line is missing in your compose:

all-in-one/docker-compose.yml

Line 5 in 4b30bcd

name: nextcloud_aio_mastercontainer # This line is not allowed to be changed

[shalak]

😅