← Directory

Lancache Bundle

Lancache Bundle is a single Docker image, whose source repository is archived, that deploys the full upstream Lancache network cache stack for homelab users,…

  • Backup
  • Other
  • Tools & Utilities
Lancache Bundle is a single Docker image, whose source repository is archived, that deploys the full upstream Lancache network cache stack for homelab users, combining DNS, monolithic cache, and SNI proxy services to accelerate repeated file downloads.

Platform availability

Available on 2 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

15/100 Low

Maintained
0GitHub repository is archived
Popular
2620 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
1016 GB minimum RAM

Availability: platform listings confirmed today, links checked 15 days ago

GitHub stars
20
Open issues
9
Last commit
2020-11-18
License
MIT
Activity
stale

Checked 7 days ago - source: GitHub (Josh5/lancache-bundle)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 8 CPU core(s), 2560 GB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 16 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install Docker first This setup expects Docker (the software that runs the containers) to already be installed on a Linux machine. If Docker is missing, the docker compose up -d command will fail before the cache can start. source
  • Set up the .env file before starting Clone the Lancache Docker Compose repo (the files that tell Docker what containers to create), fill in the .env settings file, then run docker compose up -d from that folder. The .env file controls your network and cache settings, so filling it in first helps avoid containers starting with wrong or missing values. source
  • Send router DNS only to Lancache DNS After the containers are running, tell your router to send all DNS (name-to-IP lookup) requests only to the lancache-dns container. If the router still sends DNS to other servers, devices will not use the cache. source

Fetched 11 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What should I prepare before running the Lancache Docker Compose stack?

Docker must already be installed, and the .env file should be filled in before running docker compose up -d. The .env file controls network and cache settings, so this helps avoid containers starting with wrong or missing values.

How do I make devices on my network use the Lancache DNS?

After the containers are running, point the router so all DNS requests go only to the lancache-dns container. If the router still sends DNS requests elsewhere, devices may not use the cache.

How can I test whether a client is using the Lancache?

Set one computer’s DNS to the Lancache server and then check normal web browsing plus a small Steam game download. This helps confirm the cache path is being used.

Can Lancache be run together with Pi-hole?

Yes, a community tutorial combines Lancache with Pi-hole while keeping full Pi-hole statistics.

Answers sourced from github.com, www.reddit.com, www.reddit.com

Community

Collected 11 days ago - public community threads