spants
-
Posts
637 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by spants
-
-
not sure - I use it in bridge mode and forward port 1883
-
On 9/15/2018 at 4:57 AM, stlrox said:
I installed MQTT docker container on my unRAID server but it's failed to start successfully. I noticed Docker image was pulled successfully and the container was created. I didn't change any default settings for the template. I made sure no other docker containers using these ports (1883, 9001)
How do I resolve this error?
Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='MQTT' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -p '1883:1883/tcp' -p '9001:9001/tcp' -v '/mnt/user/appdata/MQTT':'/config':'rw' 'spants/mqtt' fc6bddb7beff82df28c84b2444d6a406164a3de3005b512401e4371950de4c5d /usr/bin/docker: Error response from daemon: driver failed programming external connectivity on endpoint MQTT (07b5d4fff7293d9cc2de96ec8c1bf4d9f3f9cc26ddc822b523ebc6ceaad25288): Error starting userland proxy: listen tcp 0.0.0.0:1883: bind: address already in use. The command failed.
TIA
Do you have anything else using port 1883?
-
8 hours ago, semtex41 said:
Ok, at the suggestion of @SteelzFinest i went back and reread the thread.
This is day 5 of my deep dive and I have finally tracked down the combo to keep the container running.
If this works for anyone else, let me know and I will share it on github.
- semtex
Hi Semtex41
Thanks for the suggestions which I have now put into the master template (UID and change to eth0). I guess that many of us were not having issues due to running it before and manual tweaks etc.
The changes to the template should update shortly.
-
8 hours ago, mbezzo said:
Submitted this if others with the issue want to add on/comment: https://github.com/pi-hole/docker-pi-hole/issues/321
excellent bug reporting! Please can other people add their experiences if relevant.
-
Hi Guys
As mentioned, this is just a template for the docker image that is built here https://github.com/pi-hole/docker-pi-hole/.
Please can you raise an issue on the github?
cheers
Tony
-
On 8/14/2018 at 9:09 PM, Ford Prefect said:
...here's a Docker including the zerrotier-one controller SW and a UI implementation, ready to run your own: https://github.com/key-networks/ztncui-containerized
many thanks - will take a look
-
21 hours ago, FDM80 said:
Looks like Pi-hole v4 just came out.
It looks like they have brought diginc into the fold and have turned his work into an official docker.
I assume the unRaid template will be updated with any necessary changes.
The Template has been updated and pushed .... Check for updates in the next few hours.
Welcome to v4!
(if it didn't update for you, change the repository to: pihole/pihole:latest )
- 1
-
I managed to get it working but I cannot get a reliable way of exposing the data inside the docker as volumes on the unraid filesystem.....
@cedricverst could do with some help from you...!
-
On 7/13/2018 at 9:11 AM, cedricverst said:
Thanks for doing this!. It will make life easier. BTW, is onvif fully supported now?
-
I am looking at this again.... Will report back soon.
-
I see that someone is attempting to build a zerotier controller module for PFsense..... that would be great for me. Currently very alpha though.
-
3 hours ago, Muff said:
Hi,
First of all I just want to thank everyone involved with Pi-Hole, it's an awesome software?
I just noticed that my Pi-Hole container crashes and won't start.
I haven't done any changes that I can think of that would course this.
This is the log from the container:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific setup for docker diginc/pi-hole + [[ admin == '' ]] + pihole -a -p admin admin [✓] New password set Using custom DNS servers: 9.9.9.9 & 8.8.8.8 DNSMasq binding to custom interface: br0 /etc/pihole/setupVars.conf: line 4: 9.9.9.9: command not found [cont-init.d] 20-start.sh: exited 127. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
I've googled and searched this forum but I haven't found anything and I hope that you can help me
Thank you!
This is the problem:
/etc/pihole/setupVars.conf: line 4: 9.9.9.9: command not found
What is in your setupVars.conf file?
-
46 minutes ago, etsi said:
I have problems too, it's useless and can't trust it for dns service.
Have you also checked diginc's github page for help?
-
1 hour ago, ruvil said:
I'm not sure how often pihole is updated, but i have noticed that the docker has not been updated in a while. Is this correct? I'm just wondering since i have noticed that many other dockers update almost once weekly.
My current pihole versions are Pi-hole Version v3.3.1 Web Interface Version v3.3 FTL Version v3.0
digiinc updates his docker images quite frequently. If you check your Repository points to: diginc/pi-hole:latest
The versions of pihole that you have are the latest for the docker image.
The diginc release notes are here: https://github.com/diginc/docker-pi-hole/releases
https://store.docker.com/community/images/diginc/pi-hole/tags shows that the latest branch was updated 3 months ago.
There is a prerelease branch if you want to be brave.
Note that the versions will trail the standalone versions due to the work involved in converting them to docker images
-
3 hours ago, irandumi said:
This may be a super simple one but I just started playing with Node-Red and when utilizing the node-red-node-ping node, I can't seem to actually have it ping anything. No matter what I try (www.google.com, an ip on the network, etc), I receive a 'false' output.
I read somewhere that ping may be a root only command.
Any ideas?
I used the "manage pallete" option in node red to install node-red-node-ping. Works well.
-
8 hours ago, schford said:
Its running with it's own IP ...
Ok, have you tried the Console command on the nodered icon to install Bonjour and then node red "manage pallete" option to install homekit?
-
1 hour ago, schford said:
Hi guys,
I would love to be able to use this - https://flows.nodered.org/node/node-red-contrib-homekit-bridged so I can make my stuff availavlle to apple home.
Docker installs ok but then home app on apple never finds it I am running the docker with :V8 at the end to get latest node js
I wonder if the docker needs these added to it?
Prerequisites
These nodes are based on the extremely awesome HAP-NodeJS -Project which uses an implementation of mdns to provide Bonjour / Avahi capability. Please refer to the HAP-NodeJS Wiki and to mdns for install instructions, if you get stuck on the following.
Install
For Debian / Ubuntu you need to install the following in order to support Bonjour / Avahi
sudo apt-get install libavahi-compat-libdnssd-dev
Then run the following command in your Node-RED user directory - typically
~/.node-red
npm install node-red-contrib-homekit-bridged
Thanks for any advice
Stuart
Is nodered bridged? Try host network mode
-
Is unraid using dhcp from your router and router using unraid? If so, set static address in unraid networking and dns to 8.8.8.8 or whatever
-
Guys, any enhancements for this, please raise it against the docker owner, diginc. I just wrote a simple template for unraid.
The diginc github is here:https://github.com/diginc/docker-pi-hole
-
10 hours ago, yippy3000 said:
There seems to be a missmatch on versions in the docker. Logging/statistics keep breaking/stopping and the fix is to delete the /etc/dnsmasq.d/01-pihole.conf and restart the container
I figured this out from the developer here:
This broke again, with the same fix working to fix it, after the Unraid 6.5.3 upgrade and reboot so it makes me think that the docker has the wrong config file set as the default.
It might be worth asking here: https://github.com/diginc/docker-pi-hole/issues
The template is just a wrapper for his docker image.
-
21 hours ago, ebnerjoh said:
I tried now to create the keys within the docker, still the same result.
Do I need a special program that Node Red is able to read the certificate? I need to uncoment this "fs" setting, maybe it is this?
Br,
Johannes
The docker is the official standard one so it should work. I don't use https as it just on an internal home network .
Wondering if your paths are correct for the certs and/or permissions?
I will try and have a look over the weekend ....
-
24 minutes ago, ebnerjoh said:
Hi,
I was able to get the Node-Red docker running with my Home Assistant docker.
But I am unsure about securing Node Red with HTTPS. Are there certificates included? If I just uncommend "fs" and the "https" options I am getting an certificate error and node red is not starting.
Br,
Johannes
take a look here: https://www.hardill.me.uk/wordpress/2015/05/11/securing-node-red/
-
re the logs:
Possible fix here....
https://github.com/diginc/docker-pi-hole/issues/271#issuecomment-389591390
-
On 5/13/2018 at 4:34 PM, nuhll said:
It seems like this docker needs a way to get automatic rid of logs.
I guess the logs are located somewhere inside the docker.
I used to use the script below with the userscripts plugin to delete the logs once a day.
It looks like pihole stores a log in /var/log in the docker. The recent Docker from digiinc was supposed to put these on a volume mount.
#!/bin/bash DOCKER_NAME=pihole PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin # Download any updates from the adlists docker exec $DOCKER_NAME pihole updateGravity > /dev/null # Pi-hole: Update the Web interface shortly after gravity runs # This should also update the version number if it is changed in the dashboard repo #docker exec $DOCKER_NAME pihole updateDashboard > /dev/null # Pi-hole: Parse the log file before it is flushed and save the stats to a database # This will be used for a historical view of your Pi-hole's performance # docker exec $DOCKER_NAME dailyLog.sh # note: this is outdated > /dev/null # Pi-hole: Flush the log daily at 11:58 so it doesn't get out of control # Stats will be viewable in the Web interface thanks to the cron job above docker exec $DOCKER_NAME pihole flush > /dev/null
[SUPPORT] pihole for unRaid - Spants repo
in Docker Containers
Posted
I changed the template 2 weeks ago but it would probably (and hopefully!) not update anyones existing settings.... Note that my system works perfectly on BR0 but I understand that others have problems