node-red-docker VS docker-pihole-unbound

Feb 14 16:16:31 podhost podman\3483]: 2023-02-14 16:16:31.053466474 -0300 -03 m=+0.071815344 container health_status 2177a7448029695a17a9c0c774b8f48875bda76f6bf6e100254532765c6005d7 ()image=docker.io/nodered/node-red:3.0.2-18, name=nodered, health\status=unhealthy, org.label-schema.build-date=2022-08-04T13:19:34Z, org.label-schema.docker.dockerfile=.docker/Dockerfile.alpine, org.label-schema.vcs-type=Git, org.label-schema.license=Apache-2.0, org.label-schema.name=Node-RED, authors=Dave Conway-Jones, Nick O'Leary, James Thomas, Raymond Mouthaan, org.label-schema.vcs-url=https://github.com/node-red/node-red-docker, org.label-schema.version=3.0.2, org.label-schema.arch=, org.label-schema.description=Low-code programming for event-driven applications., org.label-schema.url=https://nodered.org, org.label-schema.vcs-ref=))

I found that Nick O'Leary (founder of Node-RED and the great guy that he is..) already did some research on this, I just had to bring this all together.

I don't use node-red, but I guess they use the node-red user in shell and overriding the process owner causes some issues with that. You can add an issue to their repository if you want.

Standard practice with Node-Red lets the user add dedicated flows and dependencies via the npm install command-line. However within the Node-Red-Docker Repo Wiki, you can also add these flows/dependencies via a dedicated package.json.

# https://nodered.org/docs/getting-started/docker # https://community.home-assistant.io/t/node-red-get-homeassistant-error/53923 node-red: container_name: node-red depends_on: homeassistant: condition: service_started environment: PGID: $PGID PUID: $PUID TZ: $TZ image: nodered/node-red networks: smarthome: ipv4_address: 172.18.0.2 restart: always # https://github.com/node-red/node-red-docker/wiki/Permissions-and-Persistence # chown volume after first run volumes: - $USERDIR2/node-red:/data

Node Red - Flow programming, mainly for IOT

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.