A ZimaBlade user reported that ZimaOS v1.4.1 could no longer install apps and displayed a Docker Hub connectivity error even though the local network itself was working. An initial suggestion to disable IPv6 did not solve it.
The eventual fix was the system clock: the user found that network time synchronization was not active, so the ZimaOS clock was incorrect. Once time synchronization was restored, Docker Hub access worked again.
Why a Wrong Clock Can Look Like a Network Error
Container registries use HTTPS. If the host clock is far from the real time, certificate validation and authenticated requests can fail in ways that look like ordinary Internet connectivity problems. That is why a working LAN connection does not rule out a time-related failure.
Check Time Before Rebuilding the Network
From a terminal, first inspect the current clock and synchronization state:
timedatectlOn a system using systemd time controls, network time synchronization can be enabled with:
timedatectl set-ntp trueThe current timedatectl NTP controls documents both the status output and the set-ntp control. The exact time service available on a particular ZimaOS build may vary, so use the command as a diagnostic rather than blindly replacing system configuration.
A Practical Docker Hub Checklist
- Confirm the ZimaOS dashboard has normal LAN connectivity.
- Check date, time, timezone, and whether the system clock is synchronized.
- Reboot after restoring time synchronization if registry requests still use stale state.
- Only then move on to DNS, IPv4/IPv6, firewall, ISP, or proxy troubleshooting.
Version Context
This report came from ZimaOS v1.4.1 in 2025. The value of the thread is the diagnostic pattern, not a claim that current ZimaOS releases have a known Docker Hub bug. The official reply explicitly said it was not a known v1.4.1 issue.
Current Time and Registry Context
The ZimaOS App Store requirements is useful when a failed application install looks like a resource or compatibility problem, while the first Docker app explains the normal application-pull workflow. If the failure appears during installation or first access on third-party hardware, the ZimaOS installation troubleshooting provides a wider network and boot diagnostic checklist.
The timedatectl NTP controls confirms that timedatectl can report whether network time synchronization is active and can enable it with set-ntp true when a compatible synchronization service is available. Docker's Docker registry certificates documents certificate-based registry authentication and TLS, which is why clock validity belongs early in the checklist when HTTPS registry access fails unexpectedly.
Bottom Line
If ZimaOS says Docker Hub is unreachable while normal network access appears fine, verify the system clock early. In this community case, NTP synchronization—not IPv6—was the decisive fix.
