Sorry for the delay, I have just restarted work so I was busy with life related stuff. My NAS box is an X86, so that might explain why I could not get PI-Hole working. I also noticed significant disk thrashing when I left pi-hole running long enough (even though I could not configure it). My personal suspicion is that some kind of permission needs to be set top allow configuration. Pi-Hole is currently uninstalled until I get more than 2G ram for the NAS box. I do plan to run memtest86 immediately after installing the additional ram. I did get docker to run by running "sudo ash" before running the docker commands. Obviously the SSH login did not provide root permission even though I used the admin account. On 6/29/2022 4:32 PM, John Stoffel wrote:
"Kevin" == Kevin Stratton via WLUG <wlug@lists.wlug.org> writes: Kevin> I am having trouble with getting pi-hole working with my Kevin> Asustore NAS.
Is this NAS box based on ARM processors? As I understand (stood?) pihole only runs on ARM based linux for some reason or other. I too looked into this a while ago, it wasn't setup at all to run on a debian x86_64 system at all.
Kevin> I think I have traced it down to an issue with Kevin> the docker install. I did verify that the docker CE (community Kevin> edition) was also installed.
Kevin> Per a tutorial about docker, I should be able to run something like Kevin> hello world and it will install. I may not have the name correctly Kevin> entered, but I do not think in this case it matters (yet)
But in general, I think you need to run docker as root so that it has the permissions to do stuff properly. But I only have one docker container running, so that's what I do.
John
Kevin> admin@AS5202T-7085:/var/run $ docker run hello-world
Kevin> docker: Got permission denied while trying to connect to the Docker Kevin> daemon socket at unix:///var/run/docker.sock: Post Kevin> "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create": dial unix Kevin> /var/run/docker.sock: connect: permission denied.
Kevin> See 'docker run --help'.
Kevin> admin@AS5202T-7085:/var/run $
Kevin> When I did a ls -l of /var/run in a ssh session, I got the following:
Kevin> srw-rw---- 1 root root 0 Jun 24 19:57 docker.sock=
Kevin> The "=" is something I am not familiar with. Could it mean that the Kevin> symbolic link is to itself?
Kevin> I could not find any references to this online and could not replicate Kevin> this experimenting with ln in my Ubuntu distribution.
Kevin> _______________________________________________ Kevin> WLUG mailing list -- wlug@lists.wlug.org Kevin> To unsubscribe send an email to wlug-leave@lists.wlug.org Kevin> Create Account: https://wlug.mailman3.com/accounts/signup/ Kevin> Change Settings: https://wlug.mailman3.com/postorius/lists/wlug.lists.wlug.org/ Kevin> Web Forum/Archive: https://wlug.mailman3.com/hyperkitty/list/wlug@lists.wlug.org/message/SQVT5E...