The 'nextcloud-aio-mastercontainer' container was not found.

[Lex1020]

Using the compose.yml file from the project's root directory gives the following errors.

Trying to fix docker.sock permissions internally...
Creating docker group internally with id 119
It seems like you did not give the mastercontainer the correct name? (The 'nextcloud-aio-mastercontainer' container was not found.)

[Acsigen]

If you use docker run please use --name nextcloud-aio-mastercontainer inside the command, before the image name.

If you use docker compose, please add container_name: "nextcloud-aio-mastercontainer" to the configuration. Also do not rename the service.

[Lex1020]

If you use docker run please use --name nextcloud-aio-mastercontainer inside the command, before the image name.

If you use docker compose, please add container_name: "nextcloud-aio-mastercontainer" to the configuration. Also do not rename the service.

container_name: nextcloud-aio-mastercontainer is already in the docker-compose file. I've used the exact docker-compose file the Readme says here: https://github.com/nextcloud/all-in-one?tab=readme-ov-file#how-to-run-aio-with-portainer

[szaimen]

See the difference between volume and container name. That is what you missed. The volume uses underscore and the container dashes...

[MCT-MIT]

Yup, walking error message. 👎
Thanks for the correction.

[joshtrichards]

Are you perhaps running rootless?

https://github.com/nextcloud/all-in-one/blob/main/docker-rootless.md

EDIT: Fixed link

[Lex1020]

Are you perhaps running rootless?

https://github.com/MarvvanPal/all-in-one/blob/main/docker-rootless.md

I'm trying to start it in Portainer. Docker has root access

[szaimen]

Hi @Lex1020 possibly you try to run it with docker swarm? See https://github.com/nextcloud/all-in-one#can-i-run-this-with-docker-swarm

[Lex1020]

I didn't run it with Docker Swarm.

[szaimen]

Hi, can you run the output of sudo docker ps; sudo docker inspect nextcloud-aio-mastercontainer here?

[Lex1020]

No. I cannot. I opened this request 10 months ago.

I don't use nextcloud anymore. Nor do I plan to.

[szaimen]

All right. I guess we can close this then

[MicheleM42]

I'll share my experience to help anyone noob like me with the same exact problem.
I noticed that using the command
docker ls -a
I didn't get any of the containers I was actively running and able to display/start/stop in portainer.

That happened because I had docker both on apt and snap.

Here's how I figured it out:
apt list --installed | grep 'docker'
--> list of all programs installed by the system
snap list
--> list of all programs installed by Snap
I had docker on both lists. So I removed one of them:
sudo snap remove docker
After restarting the system the problem was gone.

[1337haXXor]

So I've been running it in docker-compose for a while now. I decided to update nextcloud and the machine, but when doing docker-compose up, I got that error. Looking at the chosen answer, I now see that my docker-compose has the volume name and the volume section all listed as nextcloud_aio_mastercontainer (with underscores), but the container name is nextcloud-aio-mastercontainer (with hyphens). I didn't change anything, how did that happen? I tried changing the underscored ones to hyphens, and vice versa, but neither one works. How would I rectify this?