docker-nextcloud VS watchtower

I am trying to setup a Nextcloud Docker using the LSIO image(NC LSIO) as I need to have SMB/CIFS external storage support along with simplified docker-compose. I have also setup my own CA using the Step-CA ACME provisioner (Self CA using Step-CA) & use certbot on all my devices to generate the certs for all the devices & services as needed.

I did so that wasn't the solution. Found this which is similar to what you said to do, and I found out that half way through the steps it worked again but then when I went back to the latest public release it broke again. Returning to using nextcloud:24.0.6-ls204 fixed the issue so I guess I'm sticking with that from now on.

If you are running into this issue as of recent, you're probably also running NC with this container.

Since you're using the linuxserver.io docker container it should be very likely that someone else is or will be having the same problem. Like maybe this "[BUG] SMB in external storage doesn't work since the last update #303 " https://github.com/linuxserver/docker-nextcloud/issues/303

Issue

Seems that there is already an opened Bug for this one.

--- version: '3' services: app: # https://github.com/linuxserver/docker-nextcloud/releases image: lscr.io/linuxserver/nextcloud:${NEXTCLOUD_VERSION:-latest} container_name: nextcloud_app environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} volumes: - ${NEXTCLOUD_PATH}/config:/config - ${NEXTCLOUD_PATH}/data:/data - /etc/localtime:/etc/localtime:ro ports: - 3443:443/tcp # Can be commented out once cloudflare working security_opt: - no-new-privileges:true restart: unless-stopped depends_on: - mariadb - redis labels: - "com.centurylinklabs.watchtower.enable=true"

Related: https://github.com/containrrr/watchtower

> if you're using the docker image, upgrades are a breeze. Just bump the tag on the image, redeploy, and you're done.

Or you could just run Watchtower beside it and it will automatically update your docker containers. https://github.com/containrrr/watchtower If you are OK with automated updates.

So i primarily use containers on my local machine walled off from the internet, so it's not a big concern for me. Watchtower [1] is popular among home server users too which automatically updates containers to the latest image.

For production uses I think companies generally build their own containers. They would have a common base linux container and build the other containers based off that with a typical CI/CD pipeline. So if glibc is patched, it's probably patched in the base container and the others are then rebuilt. You don't have to patch each container individually, just the base. Production also minimizes the scope of containers with nothing installed except what's necessary so they have few dependencies.

[1] https://github.com/containrrr/watchtower

You can use Watchtower (https://containrrr.dev/watchtower/) that solves problem of manual pulling on VPS.

I checked https://containrrr.dev/watchtower/ and Arguments, but I don't understand where to attach that using portainer.

Again, there are options to automate some of the burden here by using tools such as Watchtower.

Have you ever deployed a Docker app on a server, but everytime you push a new version of your image to a Docker registry you need to manually restart your app? If you want to automate this restarting, this blog post is for you! I am now going to show you how you can do this with literally 1 simple command using Watchtower!