NTP

NTP is a Docker container that runs chrony on Alpine Linux, letting homelab users synchronise system clocks with upstream Network Time Protocol (NTP) servers…

  • Network Services
  • Tools & Utilities
NTP is a Docker container that runs chrony on Alpine Linux, letting homelab users synchronise system clocks with upstream Network Time Protocol (NTP) servers and provide time to other devices on the network.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (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.

38/100 Low

Maintained
12last commit 615 days ago
Popular
53445 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
75no serious findings

Based on 4 of 5 factors.

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

GitHub stars
445
Open issues
9
Last commit
2025-03-16
License
Apache-2.0
Activity
stale

Checked 21 days ago - source: GitHub (cturra/docker-ntp)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Set your WiFi name and password first Replace the example <SSID> and <PASSWORD> with your real WiFi credentials before flashing the sketch. Without them, the device cannot reach an NTP time server, so the time will not appear. source
  • Use the WiFi header that matches your board Keep the correct include line for your hardware, such as ESP8266WiFi.h for ESP8266 boards or WiFi.h for ESP32 boards. If it is wrong, the code may fail to compile or never connect. source
  • Add a timezone offset if the time is off Set the offset in seconds when creating timeClient if you want local time instead of UTC. Without it, the reported time may look like the wrong timezone. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which port should I expose for NTP clients?

Publish UDP port 123, for example with --publish=123:123/udp.

How do I configure different upstream NTP servers?

Set the NTP_SERVERS environment variable to a comma-delimited list without spaces.

Can I run the container with a more restrictive filesystem?

Yes, run it read-only and mount /etc/chrony, /run/chrony, and /var/lib/chrony as writable tmpfs mounts with mode 1750.

Does the included Compose file have a Docker Engine requirement?

The included file uses Compose format 3.9, which requires Docker Engine 19.03.0 or newer.

Can this container provide time to other devices on my network?

Yes, chrony can operate as an NTPv4 server and peer to provide a time service to other computers in the network.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads