Hello everyone,
I am looking for technical guidance on maintaining a content cache for private use on my home network.
I currently use my MacBook to handle the registration of a cache running on a Linux/Docker server. The MacBook is a regularly used laptop, so it is not always awake or connected to my home network. I would like to understand whether an older Mac mini or another device could take over this role reliably. For cost reasons, I would prefer not to purchase a Mac mini M1 or newer solely for this purpose.
The implementation I am experimenting with is Maurice’s Open Apple Cache project. It handles the actual caching on Linux and uses a small macOS helper to register the cache with Apple. I understand that this is an experimental third-party project using private macOS interfaces, rather than an Apple-supported implementation.
To clarify, I understand that the Docker-based setup is not Apple’s preferred or officially supported approach. My preferred solution would actually be to use an older Mac as a dedicated, always-on content cache, ideally running Apple’s built-in Content Caching service. The Linux/Docker setup is an experiment rather than a requirement. I would therefore particularly welcome guidance on whether an older Intel Mac could still provide a reliable solution for a household with current Apple devices, and which hardware and macOS requirements I should consider.
The recurring problem is that the cache becomes undiscoverable while the MacBook is asleep or unavailable. The Linux service continues running, its health checks remain successful, and a direct download test still produces a cache HIT. However, Apple devices no longer discover it automatically.
For example, AssetCacheLocatorUtil returned the following on the MacBook after the problem occurred:
--- Information for system services:
Checking whether there might be content caches available...
There might be content caches available.
Finding refreshed content caches supporting shared caching...
Found 0 content caches
--- Information for user 502 (results for other users may be different):
Finding refreshed content caches supporting shared caching...
Found 0 content caches
Testing all found content caches for reachability...
No content caches to test.
The helper’s status file still showed "state": "registered", but its last successful registration was approximately 13 hours old. After I manually ran the registration helper again, the cache became discoverable and was reported as healthy. No changes to the Docker service were necessary.
The helper currently runs as a LaunchAgent and attempts registration every 3,000 seconds. Its registration response reports a heartbeat interval of 3,300 seconds. I do not know whether that interval corresponds to the actual registration lifetime, so I would appreciate clarification rather than assuming a specific expiry time.
My questions are:
- What is Apple’s recommended approach for home content caching when no Mac is continuously available?
- Could an older Intel Mac mini reliably perform the registration and renewal role, even if the actual cache remains on another server?
- Is registration from a system LaunchDaemon, without an interactive user login, technically possible? Are there relevant restrictions involving AuthKit or the execution context?
- Are there public APIs, documentation, or Apple open-source components that could help implement this functionality on older hardware or another platform?
- Is there a supported way to maintain discovery during longer periods when the registering Mac is asleep or offline?
I would also appreciate Apple’s perspective on whether a project such as Open Apple Cache is a reasonable alternative for private households without an always-on Mac, or whether a different architecture would be preferable.
This is solely for sharing Apple software updates and App Store downloads among devices within my household.
Thank you for any technical guidance or pointers to relevant documentation.
Kind regards,
Philipp