port 68 in use on latest photon os

[Vv9Hx]

I use photon os to run my dockers as it advertised to do.

I want to run adguard home container today. But the docker tells me

docker: Error response from daemon: driver failed programming external connectivity on endpoint adguardhome (0c5f136cef41b65315d9d1d767e6794abd5f6fd32601056671e5d80ca2431834): Error starting userland proxy: listen udp4 0.0.0.0:68: bind: address already in use.

I did a little bit search and found this blog.

It appears he did not mention any problem about port 68.

sudo netstat -tunlp |grep 68       
udp        0      0 10.2.0.6:68             0.0.0.0:*                 576/systemd-network

systemd-network is using it. But I could not found a lot more information about it.

I am not a Linux expert, but I want to learn more about it. As this is also one reason of using photon os. Not using super popular distributions like Debian or Ubuntu will bring me more challenge and force me to solve it.

So, what does this systemd-network using 68 for? Is it possible to release the 68 port?

Do you have any suggestion for next move like some blog or materials related with photon os may help with this issue?

I know there is an easy way to just give this adguardhome container a whole separate IP to solve this. But I want to try  the complex fix first. 

[Daniel Casota]

Hi,

If dhcp+dns are already provided by your hardware router, try to make run adguard on photon os with a straight forward dhcp setup.

- stop&disable systemd.resolved
  systemctl stop systemd-resolved
  systemctl disable systemd-resolved

- modify your docker-compose.yaml file by deleting the dhcp server port entries
- "67:67/udp"
- "68:68/tcp"
- "68:68/udp"

- rerun
    be aware: the prune -a command deletes ALL existing images !
  docker system prune -a
  docker image prune -a
  docker-compose up --detach

With this, the container should be up and running eg. on port https://<ip>:3000 . A test with version v2.3.4 (aarch64) worked flawlessly.

Hope this helps.
-Daniel