NextCloudAIO + docker portainer installation trouble

[mrrubik]

Hi NC Community,

I’m trying to install NextCloudAIO through portainer and I’m not very experienced, so I’m using the default template to get a feel for things: all-in-one/compose.yaml at main · nextcloud/all-in-one · GitHub

Yet when I deploy the stack, nextcloud-aio-mastercontainer logs show:

Trying to fix docker.sock permissions internally...

Adding internal www-data to group ntp

It seems like you did not give the mastercontainer the correct name? (The 'nextcloud-aio-mastercontainer' container was not found.)

Using a different name is not supported since mastercontainer updates will not work in that case!

If you are on docker swarm and try to run AIO, see https://github.com/nextcloud/all-in-one#can-i-run-this-with-docker-swarm

The last 2 lines just repeats and the container doesn’t come up, I’ve searched and read the issue is usually with volume naming being incorrect (using hyphens instead of underscore) but I’m literally just copy/pasting the sample yaml above.

What am I missing?

[vawaver]

Personally, I don’t really recommend using Portainer to run the Nextcloud AIO Docker.

I use Nextcloud AIO + NGINX proxy (on an Ubuntu server).

Create a directory on your disk, for example, nextcloud-aio, and within it, create a file called docker-compose.yml.
Copy the content from the link I’m sharing into this file:

Docker based NextCloud AiO with nginx on separate Ubuntu VM - not working

My docker-compose.yml volumes: nextcloud_aio_mastercontainer: name: nextcloud_aio_mastercontainer services: nextcloud: image: nextcloud/all-in-one:latest restart: unless-stopped container_name: nextcloud-aio-mastercontainer volumes: - nextcloud_aio_mastercontainer:/mnt/docker-aio-config - /var/run/docker.sock:/var/run/docker.sock:ro ports: - 6789:8080 # change the port on the left side if it's already in use on your host system. environment: - APACHE_PO…

Then, start the Docker with the command, depending on the version of docker compose you have installed:

docker-compose up -d

or

docker compose up -d

[mrrubik]

Thank you! I have figured this out, it appears I had 2 Docker engines running on the server, installed via apt and snap causing conflicts.
After removing the snap instance I was able to get NextCloud up and running. Thank you!