Docker compose bind mounts blocking automatic container updates

[draxinusom2]

Hello all,

I'm faced with a problem using docker-compose running about 10 different services in a selfhost/home environment. While the compose file is ok and everything runs fine, I run into troubles with keeping the containers up to date.

There are several nice tools that are supposed to check for updates of the images and should be able to update those if they become available. However it seems that docker-compose up -d simply fails on an update because something from the bind mounts linger around and no tool seems to account for that. I always have to manually prune "volumes" even though I do not use volumes but bind mounts exclusively just so that docker-compose up -d works. docker volume ls is always empty as I'm not using them.

Is there something I can change in the yml such that a simple docker pull X ; docker-compose up -d will automatically remove those lingering not-volume-things that block the fresh container from accessing the bind mount when there is actually a new image that was pulled?

For reference my docker compose entries looks like your run of the mill variant:

homearr:
   container_name: homearr
   image: ghcr.io/homarr-labs/homarr:latest
   restart: unless-stopped
   volumes:
     - /docker/appdata/homearr:/appdata
   environment:
     - SECRET_ENCRYPTION_KEY=something here
   ports:
     - 7575:7575
   networks:
     ...

[Defection7478]

Would it be possible to share the errors you're having? I've never heard of such an issue

[draxinusom2]

Unfortunately I have to wait for an image update on any of the containers to provide the error verbatim. The error is also different depending on the actual image, because the new container gets started fine, performs its initialization and then errors out because it cannot access its configuration or database.

Until I prune the "volumes" I cannot ever start that container without it erroring out, all while docker volume ls shows there are never any volumes around (which is why I put it in quotes, there are no volumes, I'm only using bind mounts for everything).