Docker Swarm: Using a different name is not supported!

[SingingFrog7]

Hello

As anyone tried to run this container with docker swarm? I can't get it to work due to the container name not being the expected one.

I don't know if I am the only one trying to run it that way, but I have an high-available docker swarm cluster I'd like to use.

My docker-compose file:

version: "3.8"

services:
  app:
    image: nextcloud/all-in-one:latest
    volumes:
      - /mnt/docker-gfs/nextcloud/aio-config:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
    ports:
      - 86:80 # Can be removed when running behind a reverse proxy. See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md
      - 8086:8080
      - 8446:8443 # Can be removed when running behind a reverse proxy. See https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md

I tried setting the hostname of the container using hostname: nextcloud-aio-mastercontainer which didn't help.

I am getting this when trying to run the container:

nextcloud-aio_app.1.kgvj18ode4z9@swarm-1    | Trying to fix docker.sock permissions internally...
nextcloud-aio_app.1.kgvj18ode4z9@swarm-1    | Creating docker group internally with id 997
nextcloud-aio_app.1.kgvj18ode4z9@swarm-1    | It seems like you did not give the mastercontainer the correct name?
nextcloud-aio_app.1.kgvj18ode4z9@swarm-1    | Using a different name is not supported!

Anybody has an idea?
Thanks

[szaimen]

Hello, this message has nothing to do with using it with docker swarm. However using a different name for the container is indeed not supported. See https://github.com/nextcloud/all-in-one/blob/main/docker-compose.yml for a working docker-compose file.

[SingingFrog7]

I know that, but docker swarm ignore the container_name directive. Running it with the given docker-compose (which I used) gives the same result

[szaimen]

All right. After thinking a bit about this, I am not sure if it makes any sense to run AIO with docker swarm since AIO manages the containers on its own and you don't have any influence on how it is done in detail. However you might be interested in this: https://github.com/nextcloud/all-in-one/tree/main/manual-install

[SingingFrog7]

The reason is High Availability. I'll look into running it manually but I think it could be nice to support high availability for those who have clusters

I tought other people were running it with HA

[szaimen]

The reason is High Availability.

Yes, I understand but it is just not designed for this usecase...

I'll look into running it manually ...

All right, cool!

... but I think it could be nice to support high availability for those who have clusters

I Understand but as I said above it is not designed for this... But you may be able to do so by running and configuring the containers manually as suggested...
If you suceed, some documentation on this would be highly appreciated!

I tought other people were running it with HA

I don't think so honestly...