What happens when you try to connect? Are you trying to connect via external ip?
Pihole doesn't run in docker very well. Some arguments need to be entered in the container creation step and webui settings changes are reset when it is restarted. Not to mention v4 flat out didn't work on some devices.
We have released an adguard addon that works much better. I have personally switched over to adguard as well. It is a more polished product.
You can install that instead, then go to libreelec's ip at port 3000 to do the install wizard (you don't have to change any of those settings) and then it will be available at port 80
Just an update on the pihole docker addon situation.
We still do not plan on updating the pihole docker addon due to the issues listed above.
However, there is now a docker addon for adguard, which is just as good if not better.
It runs in docker much nicer than pihole. All the settings are done via the gui.
It is available in the linuxserver docker addon repo.
Here's a blog article on adguard: AdGuard Home: First Thoughts
They are spam posts that will be removed shortly
It's a public forum, so it's not easy to completely stop spammers without preventing regular users from posting as well
That's not helpful. See my previous message
Post the command you used to create the container. Likely your folder mapping is incorrect
Owncloud and nextcloud have a lot of dependencies and are not well suited to run on a minimal distro without a package manager like libreelec.
However, if you want to run nextcloud in docker, there is an addon for it in the linuxserver repo in libreelec
Iridium - that seems so weird since he is not asking for support on the addons, or compatibility with those addons. Also really hard to enforce he can uninstall/disable and repost the the log and then re-enable/install them. At the very end there is no difference we did not change anything, just made it harder to interact with people.
We can never rule out the possibility that one of those banned addons could be causing the issues as long as they are in there. A lot of those addons are very intrusive.
If they temporarily uninstall those addons and post a log, we rule out that possibility.
VPN might be advised for illegal content (which is not endorsed here), other than that there's really no reason to use it.
I have to disagree. In the US, congress allowed ISPs to sell all user data for profit.
I have my entire internet connection go through a vpn because I simply don't trust my ISP with my internet traffic data.
My vpn provider on the other hand claims they keep no data or logs, and their claims have been tested in courts multiple times where they were subpoenaed to hand over data on specific users and the only data they had was that the said user was a paying subscriber, nothing else. Therefore I trust them.
Linuxserver.io doesn't have a home assistant image, but you should be able to use their official docker image.
First, make sure you install the docker service add-on on LE, then follow the Linux directions here: Installation on Docker - Home Assistant
You can add the option --restart=unless-stopped to make it start on boot
Thanks for the reply, this is very much appreciated.
Yes, I did a manual roll of mine, not the repository one
"docker run pihole/pihole -p etc etc etc"
I found that editing the whitelist and the blacklist to be cumbersome via the GUI, when I have over 50 of each. Therefore, I manually edited the .txt file via the interactive shell, solving the problem.
I want to ask you a very stupid question and I really hope you can reply, I'm dumb at docker and this stuff is killing me.
I did *not* specify external folder mappings,due to testing / lazyness.
Therefore, my blacklist.txt and whitelist.txt are mounted INSIDE the docker container (yeah? is that how it works?)
So would I be right in thinking, in my situation, it's impossible for me, to upgrade my container, without losing my settings, because the settings are INSIDE the image?
(Also, I thought images were read only and any changes I make are actually never committed, so I'm kinda surprised editing the 2 files worked?)
Thanks for your time, sorry, this is kind of elementary docker advice really, I have been reading about docker for weeks and still don't 'get' how the file structure works and how data is stored.
Images are read only. But you create a container from the image, which is rw, and ephemeral. Any changes you make are inside the container. Once you destroy the container, your changes are lost.
You can copy your files out of there via "docker cp" before you destroy it
Hello I am trying to run domoticz on boot as a docker container, so I have the following "domoticz.service" file in /storage/.config/system.dCode
- Description=Domoticz Container
- ExecStart=/storage/.kodi/addons/service.system.docker/bin/docker start domoticz
- ExecStop=/storage/.kodi/addons/service.system.docker/bin/docker stop domoticz
After a reboot the domoticz container starts (I can see it running from "docker ps" command), but after some seconds it suddenly stops. If I enable the parameter "Restart" to "Allways" the docker container keeps starting and stopping in a loop.
If I check the container logs with the command "docker logs domoticz", I get the following:Code
- [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] done.
- [cont-init.d] executing container initialization scripts...
- [cont-init.d] 10-adduser: executing...
- usermod: no changes
- _ ()
- | | ___ _ __
- | | / __| | | / \
- | | \__ \ | | | () |
- |_| |___/ |_| \__/
- Brought to you by linuxserver.io
- We gratefully accept donations at:
- User uid: 0
- User gid: 0
- [cont-init.d] 10-adduser: exited 0.
- [cont-init.d] 30-config: executing...
- [cont-init.d] 30-config: exited 0.
- [cont-init.d] 99-custom-scripts: executing...
- [custom-init] no custom scripts found exiting...
- [cont-init.d] 99-custom-scripts: exited 0.
- [cont-init.d] done.
- [services.d] starting services
- [services.d] done.
- 2019-05-20 12:29:53.084 Status: Domoticz V4.10740 (c)2012-2019 GizMoCuz
- 2019-05-20 12:29:53.084 Status: Build Hash: 34b73c19, Date: 2019-05-12 18:47:31
- 2019-05-20 12:29:53.085 Status: Startup Path: /var/lib/domoticz/
- 2019-05-20 12:29:53.648 Sunrise: 06:54:00 SunSet: 21:29:00
- 2019-05-20 12:29:53.648 Day length: 14:35:00 Sun at south: 14:11:00
- 2019-05-20 12:29:53.648 Civil twilight start: 06:22:00 Civil twilight end: 21:60:00
- 2019-05-20 12:29:53.648 Nautical twilight start: 05:43:00 Nautical twilight end: 22:39:00
- 2019-05-20 12:29:53.648 Astronomical twilight start: 04:59:00 Astronomical twilight end: 23:23:00
If I run the ExecStart command manually it works perfectly. What is wrong?
Why don't you use the docker addon?
LE on VMs already work as long as the gpu is passed through correctly.
The problem is the virtual graphics drivers. Only the VMware virtual graphics driver is supported in the ova.
But passthrough graphics work. I ran LE that way via kvm for years
So, what is the suggested route now to install pi-hole: add-on or container?
Addon is easier to set up, it still works, but is on an older version.
Setting it up manually will get you the latest version, but may not work on some arm boxes out of the box and require some manual steps to fix it.
I would suggest trying the manual method first and if you have issues, use the addon.
Please don't take my question as criticism, thank you for the hard work.
I am fine with getting it manually, (mind you, I did that and it seemed to grab the latest version and it works fine)
Not at all. I just wanted to clarify that it was a deliberate decision to hold it back, and that we didn't abandon it
I didn't update the addon version for a couple of reasons.
1. The latest version image simply didn't work on a lot of arm boxes.
2. They changed how a lot of the settings are input, leading to any web gui settings changes reverting back every time the container is restarted
They contracted Baylibre to develop mainline Linux support which was topic of Linuxcon 2017/2018.
I'm not sure if everything needed on the video side is already done.
Afaik, libreelec is working closely with baylibre on that, but it is an ongoing effort. There are development builds for various arm devices including s905x with mainline kernel. Just not ready for primetime yet