docker-cloudflared VS node-red-docker

Edit: Also great to see that AGH has secure DNS built in. My Pi-Hole solution required cloudflared [0] for that.

[0]https://github.com/crazy-max/docker-cloudflared

You can forward all unresolved DNS requests to Cloudflare on Pi-hole, but if you want to send them through DNS over HTTPS (DoH) on your network, you will need to forward them to something running cloudflared. Here are 2 docker containers you can use to host on separate network containers: https://github.com/crazy-max/docker-cloudflared, https://github.com/visibilityspots/dockerfile-cloudflared

There are multiple types of encrypted DNS services (DoH, DoT, DoQ). I have used DoH using cloudflared. If you are using Docker, you can use this.

My ISP was doing the same thing. It was only fixed after switching to DoH. OP, if you are using docker, you can use this one file solution to setup pihole+cloudflared. Repo source

Cloudflared - DNS over HTTPS client that's not tied to Cloudflare (route Pihole requests through this)

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