docker-nextcloud VS docker

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"

Am I better off using this container: https://hub.docker.com/_/nextcloud/

It looks like I'm not the only person who has faced this. apache-based images require buster, for instance, and some docker images that rely on Ruby face issues too (for example, I decided to try setting up Postal but it looks like it's facing the same issues).

If you look at the info on https://hub.docker.com/_/nextcloud, you'll see that you aught to be specifying at least one volume, so that you have the data you want to not disappear on restart, and can access config files.

Yes, and this is what L passed through as the env variables in the docker compose file, as the docs state: https://hub.docker.com/_/nextcloud

You can't map binaries from host to container like this. What you need is a custom Dockerfile that installs ffmpeg. https://github.com/nextcloud/docker/blob/master/.examples/dockerfiles/full/fpm/Dockerfile

A good example to start with is at https://github.com/nextcloud/docker/tree/master/.examples/docker-compose/insecure/postgres/apache

Nextcloud is free and open source. The easiest way to install it is via docker containers. nextcloud docker