Replies: 6 comments
-
Tbh, I have no idea what could be causing this:( |
Beta Was this translation helpful? Give feedback.
-
fair enough, if you want, close it. I gave up on the docker now and moved it to a virtual machine again. Or leave it open in case someone else has the same issue. |
Beta Was this translation helpful? Give feedback.
-
Well, let's keep it open for some time until stale bot closes it |
Beta Was this translation helpful? Give feedback.
-
Any idea on this - i have the same issue? |
Beta Was this translation helpful? Give feedback.
-
Same issue here. For some reason the suggested troubleshooting article of modifying resolved daemon for docker won’t work on qnap because they don’t use systemd or the resolve daemon they use some other driver or whatever they call it ( still learning Linux systems). However one solution is to use bridge networking where docker container has it own MAC address and thereby it’s own lan ip therefore able to bind on the port .. sadly have t yet been able to get an ipv6 address for the docker container |
Beta Was this translation helpful? Give feedback.
-
Hey, I had the same problem and I found a solution. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to install AdGuard Home as a docker image on a QNAP Container station.
It works fine to install it and then run it, but it fails to stop and re-start the docker image due to the following error:
[fatal] couldn't start forwarding DNS server: couldn't listen to UDP socket, cause: listen udp 192.168.1.91:53: bind: cannot assign requested address
Prerequisites
Issue Details
Screenshots
Here is the docker terminal log on restart:
Here is the initial start:
Here is the AdGuardHome.yaml
Beta Was this translation helpful? Give feedback.
All reactions