docker-pihole-unbound VS docker-nextcloud

I'm running the chriscrowe 'one container' build for pihole for ad-blocking (https://github.com/chriscrowe/docker-pihole-unbound), and unbound for private recursive DNS which is running great on my Zima board.

I believe my problem stems from when I tried to install the pihole-unbound container (https://github.com/chriscrowe/docker-pihole-unbound)

I've got lucky enough that I could get in Nov-19 a Raspberry Pi 4 with 4GB of RAM that I use as a NAS+Pi-Hole + Unbound +Other stuff (running Void MUSL of course) and instead of an SD I use an HDD for the OS + a 5TB HDD for the data and even fully loaded all cores it barely consumes more than 22W.

I was only able to get pihole macvlan approach working with an ssh access + docker-compose approach. I used the crowe one-container approach Still had to enable Open vSwitch for the network in Synology first.

You can follow the doc to do those install steps within your own Dockerfile. Or you can use the commonly recommended chriscrowe image, which does what I’m describing.

When I started experimenting with this topic chriscrowe's was a baseline for stuff that I tryed out, so kudos to chris!

It seems you’re looking at a wrong file. Here is a docker file for one-container solution: https://github.com/chriscrowe/docker-pihole-unbound/blob/55c88afaf8d76958923adc38f4c12a80e1cb9084/one-container/pihole-unbound/Dockerfile

2) you can use something like this maintained GitHub repo. Just decide if you want to use 1 or 2 containers and modify the ip and gateways, etc accordingly.

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"