Mastercontainer and aio container do not start after updating docker

ℹ️ Support
, , ,
1

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 32.0.3
  • Operating system and version (e.g., Ubuntu 24.04):
    • Linux LMDE 7 Gigi
  • Web server and version (e.g, Apache 2.4.25):
    • Apache 2.4.65
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • Nginx 2.13.5
  • Docker version
    • 29.1.4
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • After updating docker within the LMDE Update Manager
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • Yes for domain resolutions

Summary of the issue you are facing:

After I updated docker with the LMDE update manager four days ago, my mastercontainer showed as unhealthy upon running docker ps, and taking it down and bringing it back up again did not fix it. I saw there was yet another update for docker in the update manager so I ran it, and after that the container wouldn’t even show in my list of running containers. I went to the compose file location and ran docker compose up -d, and it gave me an error saying “No services to build”. The compose file was working perfectly fine before the updates, so I’m guessing some change within docker caused it. While I was trying to fix it, I ran docker pull while inside the directory of the compose file for the mastercontainer, and it updated the files for the aio. After that, the aio stopped running and it too shows as unhealthy when starting it again.

Something to note: All my other docker containers continue to start by themselves and run healthily. If I update any of them with docker pull, will they too start showing as unhealthy?

Steps to replicate it (hint: details matter!):

  1. Update docker

  2. mastercontainer shows as unhealthy. Update docker again

  3. mastercontainer no longer shows under active containers. Bringing up the compose file now shows the error “No services to build”

  4. Pull current files within mastercontainer compose file directory, aio is updated. After starting the aio again, it too starts showing as unhealthy.

2

Hi, can you post the output of sudo docker logs nextcloud-aio-mastercontainer here?

3

image

The mastercontainer isn’t running and doesn’t show under docker ps. Also, the aio now shows as healthy, but it’s still inaccessible (502 bad gateway when going to the link)

4

Hm, then you probably need to recreate the mastercontainer

5

Would that clear any data or files I have within the server?

6

As long as you do not delete the nextcloud_aio_mastercontainer docker volume, it should re-use the existing data.

7

How do I recreate it then? Also how can I avoid this in the future

8

Simply use the command or compose file again that you initially used to spin-up the mastercontainer

9

That compose file is the one I’m having issues starting. Nothing has changed on it since updating docker, but whenever I try to run docker compose up -d on it, it says “No services to build”.

10

Fixed, I had to rename the mastercontainer compose file to docker-compose.yaml and spin it up again. It was previously named compose.yaml, which is strange because in the current documentation it states that compose.yaml is the NEWER standard, and docker-compose.yaml is supported for backwards compatibility. Regardless, running sudo docker compose -f compose.yaml up -d also would’ve worked instead of running sudo docker compose up -d.

Another facepalm moment for me. Thanks to the goat szaimen for the speedy replies.

11

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.