11notes/chrony

By 11notes

β€’Updated 6 months ago

run chrony rootless and distroless.

Image
Buildkit cache
Networking
1

6.3K

11notes/chrony repository overview

banner

⁠CHRONY

size5pxpulls5px5pxswiss_made

run chrony rootless and distroless.

⁠INTRODUCTION πŸ“’

chrony is a versatile implementation of the Network Time Protocol (NTP). It can synchronise the system clock with NTP servers, reference clocks e.g. GPS receiver), and manual input using wristwatch and keyboard.

⁠SYNOPSIS πŸ“–

What can I do with this? Run chrony as an NTP server for your network, pure and simple, maximized for performance and security. If you plan to run this in production, make sure you stand up multiple NTP instances and put them behind a load balancer and use virtual IPs. Pair this image with a GPS USB antenna and you can run your own Stratum 1 NTP for your entire network.

⁠UNIQUE VALUE PROPOSITION πŸ’Ά

Why should I run this image and not the other image(s) that already exist? Good question! Because ...

  • ... this image runs rootless⁠ as 1000:1000
  • ... this image has no shell since it is distroless⁠
  • ... this image is auto updated to the latest version via CI/CD
  • ... this image has a health check
  • ... this image runs read-only
  • ... this image is automatically scanned for CVEs before and after publishing
  • ... this image is created via a secure and pinned CI/CD process
  • ... this image is very small

If you value security, simplicity and optimizations to the extreme, then this image might be for you.

⁠COMPARISON 🏁

Below you find a comparison between this image and the most used or original one.

imagesize on diskinit default asdistroless⁠supported architectures
11notes/chrony2MB1000:1000βœ…amd64, arm64, armv7
dockurr/chrony15MB0:0❌amd64, arm64, armv7

⁠VOLUMES πŸ“

  • /chrony/etc - Directory of your config

⁠DEFAULT CONFIG πŸ“‘

pool ch.pool.ntp.org iburst maxsources 5
pool ntp.ubuntu.com iburst maxsources 5
maxupdateskew 10.0
makestep 1 -1
clientloglimit 268435456
driftfile /run/chrony/drift
allow all

⁠COMPOSE βœ‚οΈ

name: "chrony"
services:
  app:
    image: "11notes/chrony:4.8"
    read_only: true
    environment:
      TZ: "Europe/Zurich"
    volumes:
      - "etc:/chrony/etc"
    ports:
      - "123:123/udp"
    tmpfs:
      # tmpfs volume because of read_only: true
      - "/run/chrony:mode=0770,uid=1000,gid=1000"
    sysctls:
      # allow rootless container to access ports < 1024
      net.ipv4.ip_unprivileged_port_start: 123
    restart: "always"

volumes:
  etc:

To find out how you can change the default UID/GID of this container image, consult the RTFM⁠.

⁠DEFAULT SETTINGS πŸ—ƒοΈ

ParameterValueDescription
userdockeruser name
uid1000user identifier⁠
gid1000group identifier⁠
home/chronyhome directory of user docker

⁠ENVIRONMENT πŸ“

ParameterValueDefault
TZTime Zone⁠
DEBUGWill activate debug option for container image and app (if available)

⁠MAIN TAGS 🏷️

These are the main tags for the image. There is also a tag for each commit and its shorthand sha256 value.

⁠There is no latest tag, what am I supposed to do about updates?

It is my opinion that the :latest tag is a bad habbit and should not be used at all. Many developers introduce breaking changes in new releases. This would messed up everything for people who use :latest. If you don’t want to change the tag to the latest semver⁠, simply use the short versions of semver⁠. Instead of using :4.8 you can use :4. Since on each new version these tags are updated to the latest version of the software, using them is identical to using :latest but at least fixed to a major or minor version. Which in theory should not introduce breaking changes.

If you still insist on having the bleeding edge release of this app, simply use the :rolling tag, but be warned! You will get the latest version of the app instantly, regardless of breaking changes or security issues or what so ever. You do this at your own risk!

⁠REGISTRIES ☁️

docker pull 11notes/chrony:4.8
docker pull ghcr.io/11notes/chrony:4.8
docker pull quay.io/11notes/chrony:4.8

⁠UNRAID VERSION 🟠

This image supports unraid by default. Simply add -unraid to any tag and the image will run as 99:100 instead of 1000:1000.

⁠NOBODY VERSION πŸ‘»

This image supports nobody by default. Simply add -nobody to any tag and the image will run as 65534:65534 instead of 1000:1000.

⁠SOURCE πŸ’Ύ

⁠PARENT IMAGE πŸ›οΈ

This image is not based on another image but uses scratch⁠ as the starting layer. The image consists of the following distroless layers that were added:

⁠BUILT WITH 🧰

⁠GENERAL TIPS πŸ“Œ

  • Use a reverse proxy like Traefik, Nginx, HAproxy to terminate TLS and to protect your endpoints
  • Use Let’s Encrypt DNS-01 challenge to obtain valid SSL certificates for your services

⁠ElevenNotesℒ️

This image is provided to you at your own risk. Always make backups before updating an image to a different version. Check the releases⁠ for breaking changes. If you have any problems with using this image simply raise an issue⁠, thanks. If you have a question or inputs please create a new discussion⁠ instead of an issue. You can find all my other repositories on github⁠.

created 03.02.2026, 07:35:41 (CET)

Tag summary

Content type

Image

Digest

sha256:257e5768e…

Size

1.4 MB

Last updated

6 months ago

docker pull 11notes/chrony:4.8-nobody