Can anyone help me with this issue? i've cloned github/lancache containers, and i've docker-compose up -d,
the cache is working properly, but when i cache a game, i open another client to pull the downloaded game via the cache server, it always stuck at 99% until i remove the dns on the client of the cache server and restart steam then it continues to 100%
another issue, since i managed properly to clone github/lancache containers, and since they're working properly, whenever i restart the cache server or i turn it off then back on later, the dockers doesnt start automatically( lancache_DNS_1 and Monolithic containers, and sometimes they loop restart automatically until i disable docker.io and docker.secket etc...
that's my docker-compose.yml
x-restart-policy: &restart-policy "no"
services:
dns:
image: lancachenet/lancache-dns:latest
env_file: .env
restart: *restart-policy
ports:
- ${DNS_BIND_IP}:53:53/udp
- ${DNS_BIND_IP}:53:53/tcp
HTTPS requests are now handled in monolithic directly
you could choose to return to sniproxy if desired
sniproxy:
image: lancachenet/sniproxy:latest
env_file: .env
restart: *restart-policy
ports:
- 443:443/tcp
monolithic:
image: lancachenet/monolithic:latest
env_file: .env
restart: *restart-policy
ports:
-
Can anyone help me with this issue? i've cloned github/lancache containers, and i've docker-compose up -d,
the cache is working properly, but when i cache a game, i open another client to pull the downloaded game via the cache server, it always stuck at 99% until i remove the dns on the client of the cache server and restart steam then it continues to 100%
another issue, since i managed properly to clone github/lancache containers, and since they're working properly, whenever i restart the cache server or i turn it off then back on later, the dockers doesnt start automatically( lancache_DNS_1 and Monolithic containers, and sometimes they loop restart automatically until i disable docker.io and docker.secket etc...
that's my docker-compose.yml
x-restart-policy: &restart-policy "no"
services:
dns:
image: lancachenet/lancache-dns:latest
env_file: .env
restart: *restart-policy
ports:
- ${DNS_BIND_IP}:53:53/udp
- ${DNS_BIND_IP}:53:53/tcp
HTTPS requests are now handled in monolithic directly
you could choose to return to sniproxy if desired
sniproxy:
image: lancachenet/sniproxy:latest
env_file: .env
restart: *restart-policy
ports:
- 443:443/tcp
monolithic:
image: lancachenet/monolithic:latest
env_file: .env
restart: *restart-policy
ports:
-