Docker Community Forums

Share and learn in the Docker community.

Lancachenet/monolithic Local DNS Issue with Ubuntu 18.04

I have set up lancachenet/monolithic on Ubuntu Server 18.04 using the following script (derived from example instructions):

docker run --restart unless-stopped --name lancache-dns --detach \
  -p \
  -p \
  -e USE_GENERIC_CACHE=true -e LANCACHE_IP="" lancachenet/lancache-dns:latest
docker run \
  --restart unless-stopped \
  --name lancache \
  --detach \
  -v /cache/data:/data/cache \
  -v /cache/logs:/data/logs \
  -e UPSTREAM_DNS="" \
  -e CACHE_MEM_SIZE=4000m \
  -p \
  -p \
docker run --restart unless-stopped --name sniproxy --detach \
  -p \
  -p \

With default Ubuntu Server, this will fail because systemd-resolved is already listening on port 53. Long story short, I disabled Systemd-Resolved and got the lan-cache running as a replacement

But the lancachenet/monolithic container is immediately and continuously restarting each time it sort-of starts. I notice it is trying to listen on port 443. So is the sniproxy. The sniproxy needs to, and the lancache needs not to. I wonder if the lancache is failing to start because it can’t get the port it mistakenly thinks it needs?

For a brief second every 60 seconds, I can gather this info:

CONTAINER ID        IMAGE                             COMMAND                  CREATED              STATUS              PORTS                                                      NAMES
f106a1f66b87        lancachenet/sniproxy:latest       "/scripts/bootstrap.…"   34 seconds ago       Up 32 seconds>443/tcp,>443/tcp        sniproxy
e193af15121e        lancachenet/monolithic:latest     "/bin/bash -e /init/…"   44 seconds ago       Up 1 second>80/tcp,>80/tcp, 443/tcp   lancache
faa271c246dc        lancachenet/lancache-dns:latest   "/bin/bash -e /init/…"   About a minute ago   Up About a minute>53/udp,>53/udp            lancache-dns

Any thoughts or help on any of this would be much appreciated.