name: monolithic
services:
monolithic:
image: Package monolithic · GitHub
container_name: lancache
restart: unless-stopped
cpu_shares: 90
environment:
- CACHE_DISK_SIZE=1000g
- CACHE_INDEX_SIZE=500m
- CACHE_MAX_AGE=30d
- NGINX_LOG_TO_STDOUT=false
- PGID=1000
- PUID=1000
- UPSTREAM_DNS=192.168.0.146
- TZ=America/New_York
volumes:
- /DATA/AppData/lancache/cache:/data/cache
- /DATA/AppData/lancache/logs:/data/logs
networks:
lancache_net:
ipv4_address: 192.168.0.150
deploy:
resources:
limits:
memory: 48g
networks:
lancache_net:
driver: macvlan
driver_opts:
parent: eth1 #
Change if your interface is not eth0
ipam:
config:
- subnet: 192.168.0.0/24
gateway: 192.168.0.1
im trying to use this lancavhe docker to run with pihole and NOT break nginx
Your setup will work with Pi-hole and will not break your main NGINX, as long as you keep Lancache isolated.
You’re using macvlan with its own IP (192.168.0.150), this is correct.
That gives Lancache its own address, so it does not fight for port 80 on your ZimaOS host.
What you must ensure:
- 192.168.0.150 is not already used by another device
parent: eth1 is the correct network interface on your ZimaOS system
- Pi-hole DNS points cache domains to 192.168.0.150
- Do NOT use host network mode
- Do NOT reverse proxy Lancache through your existing NGINX
Traffic should look like this:
Client > Pi-hole (DNS) > 192.168.0.150 (Lancache)
Your main NGINX container remains separate and untouched.
If those conditions are met, it will run cleanly on ZimaOS.
o you think something like this would help? GitHub - DjoSmer/pi-hole-with-lancache-docker: If you use uklans/cache-domains or Lancache-dns this project is for you. if so how can i cleanly swap out pihole for this new one and use lancache but just the monolithic part and us ethe docker pasted to add the domain list?