lancachenet / monolithic

A monolithic lancache service capable of caching all CDNs in a single instance
https://hub.docker.com/r/lancachenet/monolithic
Other
746 stars 75 forks source link

Client is offline with server as DNS #82

Closed peduso closed 4 years ago

peduso commented 4 years ago

Hi there, thank you for building this lancache!!

I set up a Server with Linux Ubuntu 18.4.03

Then i used this tutorial: https://hoerli.net/lancache-der-cache-server-fuer-dein-netzwerk/ It is in german, but the commands are printed there.

The docker seems to be up and running. But when I change my client PC (Windows) to use the new server as DNS all Internet is gone. I can't find any website or log on my Steam.

root@server:/home/peter# hostname -I 192.168.2.12 172.17.0.1

How are you running the container(s)?

DNS Configuration

sudo apt install curl -y

sudo curl -sSL https://get.docker.com/ | sh

docker run --restart unless-stopped --name lancache -v /cache/data:/data/cache -v /cache/logs:/data/logs -p 192.168.2.12:80:80 lancachenet/monolithic:latest

docker run --restart unless-stopped --name lancache-dns -p 192.168.2.12:53:53/udp -e USE_GENERIC_CACHE=true -e LANCACHE_IP=192.168.2.12 lancachenet/lancache-dns:latest

docker run --restart unless-stopped --name lancache-sniproxy -p 192.168.2.12:443:443 lancachenet/sniproxy:latest

<!-- Paste your docker run command for the DNS container OR explain how you have setup DNS on your network to point to the container -->

Output of container(s)

I don't know what to paste here.

The server is still able to connect to the web and to ping google.com or whatever.

Do you have any idea how to solve this? What did I do wrong.

peduso commented 4 years ago

docker.service - Docker Application Container Engine Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2019-12-27 17:54:40 UTC; 50min ago Docs: https://docs.docker.com Main PID: 18198 (dockerd) Tasks: 37 CGroup: /system.slice/docker.service ├─18198 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock └─22519 /usr/bin/docker-proxy -proto tcp -host-ip 192.168.2.12 -host-port 443 -container-ip 172.17.0.2 -container-port 443

Dez 27 17:54:39 server dockerd[18198]: time="2019-12-27T17:54:39.534799213Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address" Dez 27 17:54:39 server dockerd[18198]: time="2019-12-27T17:54:39.983417513Z" level=info msg="Loading containers: done." Dez 27 17:54:40 server dockerd[18198]: time="2019-12-27T17:54:40.062447259Z" level=info msg="Docker daemon" commit=633a0ea838 graphdriver(s)=overlay2 version=19.03.5 Dez 27 17:54:40 server dockerd[18198]: time="2019-12-27T17:54:40.062651294Z" level=info msg="Daemon has completed initialization" Dez 27 17:54:40 server dockerd[18198]: time="2019-12-27T17:54:40.135564621Z" level=info msg="API listen on /var/run/docker.sock" Dez 27 17:54:40 server systemd[1]: Started Docker Application Container Engine. Dez 27 17:56:33 server dockerd[18198]: time="2019-12-27T17:56:33.788156435Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="events.TaskDelete" Dez 27 17:56:33 server dockerd[18198]: time="2019-12-27T17:56:33.961702534Z" level=warning msg="806773f9f8e57fa8f0fb86c8a9a89dca4c8d23302a7458449c64fbd96251af18 cleanup: failed to unmount IPC: umount /var/lib/docker/containers/806773f9f8e57fa8f0fb86c Dez 27 17:59:31 server dockerd[18198]: time="2019-12-27T17:59:31.370649128Z" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="events.TaskDelete" Dez 27 17:59:31 server dockerd[18198]: time="2019-12-27T17:59:31.545574466Z" level=warning msg="156575318a8f44f8abdca40e8b27c2ab6efa9bb3adcc33346f8ff820bc192f85 cleanup: failed to unmount IPC: umount /var/lib/docker/containers/156575318a8f44f8abdca40 ~ ~ ~ ~

peduso commented 4 years ago

another hint maybe: While starting the server it gives this message:

"A start job is running for Wait for Network to be Configured"

systemctl show -p WantedBy network-online.target

gives

WantedBy=docker.service cloud-config.service cloud-final.service open-iscsi.serv

peduso commented 4 years ago

my fault. not all containers startet after reboot....works fine now