unbound-docker
Unbound DNS Server Docker Image (by MatthewVance)
node-red-docker
Repository for all things Node-RED and Docker related (by node-red)
unbound-docker | node-red-docker | |
---|---|---|
13 | 8 | |
511 | 453 | |
- | 0.2% | |
6.2 | 6.9 | |
12 days ago | 21 days ago | |
Shell | Shell | |
MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
unbound-docker
Posts with mentions or reviews of unbound-docker.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-13.
-
No internet access for containers co-hosted with pihole
version: "3" # More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/ networks: dns_net: driver: bridge ipam: config: - subnet: 10.2.0.0/24 services: pihole: depends_on: [unbound] container_name: pihole image: pihole/pihole:latest hostname: pihole networks: dns_net: ipv4_address: 10.2.0.100 ports: - "5335:53/tcp" - "5335:53/udp" - "7000:80/tcp" environment: TZ: ${TZ} WEBPASSWORD: ${PWD} FTLCONF_LOCAL_IPV4: ${HOST_IP} # Set to server's LAN IP, used by web block modes. PIHOLE_DNS_: 10.2.0.200 # Upstream DNS server(s) for Pi-hole to forward queries to, separated by a semicolon DNSMASQ_LISTENING: all # "Listen on all interfaces, permit all origins" # Volumes store your data between container upgrades volumes: - /var/lib/docker/volumes/pihole/etc-pihole:/etc/pihole - /var/lib/docker/volumes/pihole/etc-dnsmasq.d:/etc/dnsmasq.d healthcheck: disable: true restart: unless-stopped unbound: # https://github.com/MatthewVance/unbound-docker container_name: unbound image: mvance/unbound:latest hostname: unbound networks: dns_net: ipv4_address: 10.2.0.200 ports: - "${HOST_IP}:53:53/udp" - "${HOST_IP}:53:53/tcp" healthcheck: disable: true restart: unless-stopped
-
I've created a simple 2 container Pihole + Unbound Docker Setup for you to use
I'm not an unbound expert, but as far as I understand MatthewVance's image, unbound is already configured properly: https://github.com/MatthewVance/unbound-docker/blob/master/1.17.1/data/unbound.sh. I didn't want to go into detail how pi-hole or unbound works, since I think there is enough documentation on that.
-
Problems with unbound
I am successfully running pihole on a different machine, but am planning to migrate to a new docker host. I figured this would be a good time to configure pihole with unbound. I am attempting to run unbound in a docker container running on Opensuse leap and I am using this docker image.
- Need help w/ unbound
-
Pihole with Recursive DNS
You can also use Unbound for recursive DNS in a docker container: https://github.com/MatthewVance/unbound-docker
- Pihole & Unbound Docker?
- Starting Unbound in a Docker Container
-
When using Unbound can’t connect to any site?
https://github.com/MatthewVance/unbound-docker/blob/master/1.14.0/data/unbound.sh
- Nothing but issues with unbound and dont know what to do.
-
Radarr installation fails on fresh Ubuntu install
# https://github.com/MatthewVance/unbound-docker unbound: container_name: unbound environment: PGID: $PGID PUID: $PUID TZ: $TZ image: mvance/unbound networks: smarthome: ipv4_address: 172.18.0.6 restart: always
node-red-docker
Posts with mentions or reviews of node-red-docker.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-02-14.
-
podman unhealthy for image nodered/node-red:3.0.2-18
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=))
- Error after 3.0 Update
- Unraid root user error
-
Use htpasswd to secure your node-RED Container
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.
-
How does the --user option (or compose equivalent) differ from LinuxServer's PUID/PGID Environment Variables?
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.
-
Create a custom Node-Red Docker Image and performance Integration Tests and CI/CD Pipelines
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.
-
Radarr installation fails on fresh Ubuntu install
# 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
-
Is this the ultimate self-hosting setup? I think so...
Node Red - Flow programming, mainly for IOT
What are some alternatives?
When comparing unbound-docker and node-red-docker you can also consider the following projects:
docker-pihole-unbound - Run Pi-Hole + Unbound on Docker
FlareSolverr - Proxy server to bypass Cloudflare protection
dnscrypt-server-docker - A Docker image for a non-censoring, non-logging, DNSSEC-capable, DNSCrypt-enabled DNS resolver
caddy-docker-proxy - Caddy as a reverse proxy for Docker
unbound-config - fragmented configuration files for unbound recursive dns resolver
docker-radarr
unbound-docker-rpi - Run Unbound with latest version of OpenSSL on Raspberry Pi with Docker.
rhasspy - Offline private voice assistant for many human languages
docker-pi-hole - Pi-hole in a docker container
docker-duplicati
unbound-docker vs docker-pihole-unbound
node-red-docker vs FlareSolverr
unbound-docker vs dnscrypt-server-docker
node-red-docker vs caddy-docker-proxy
unbound-docker vs unbound-config
node-red-docker vs docker-radarr
unbound-docker vs unbound-docker-rpi
node-red-docker vs rhasspy
unbound-docker vs docker-pi-hole
node-red-docker vs docker-pi-hole
unbound-docker vs docker-radarr
node-red-docker vs docker-duplicati