Files
chrony/README.md
GianLuca Vagnuzzi 786ecee200
All checks were successful
Update Docker Hub Description / dockerHubDescription (push) Successful in 42s
Docker Image CI / build_docker_images (push) Successful in 20m3s
Upgraded Alpine to v.3.23.0 & chrony 2 v.4.8-r1
2025-12-04 16:20:55 +01:00

54 lines
1.3 KiB
Markdown

# Chrony
Chrony server based on Alpine Linux.
## Quick reference
* Where to file issues:
[Gitea](https://git.gmmg.it/kom23/chrony/issues)
* Supported architectures: amd64 , armv7 , arm64v8
## How to run
### With docker run
```
docker run -di --network host -e ALLOW_CIDR=0.0.0.0/0 rardcode/chrony
```
### With docker-compose file
```
services:
app:
image: rardcode/chrony
container_name: chrony
environment:
- ALLOW_CIDR=0.0.0.0/0 # clients to connect and get the time. Default is none.
#- NTP_SERVER=time.inrim.it # The NTP server to get the time to set from. Default is pool.ntp.org.
#- SYNC_RTC=false # Sync the realtime clock on the machine/instance the service is running. Default is true.
network_mode: host # Recommended so that clients come with the real ip, otherwise they would all get with only ip, that of the docker
cap_add:
- SYS_TIME
restart: unless-stopped
```
Useful commands:
```
docker exec chrony /bin/sh -c "chronyc clients"
docker exec chrony /bin/sh -c "chronyc sources"
```
## Changelog
v1.23.8 - 04.12.2025
- Alpine v. 3.23.0
- chrony v. 4.8-r1
v1.0.2 - 09.10.2025
- Alpine v. 3.22.2
v1.0.1 - 14.08.2025
- Alpine v. 3.22.1
- chrony v. 4.6.1-r1
v1.0.0 - 25.06.2025
- Alpine v. 3.22.0
- chrony v. 4.6.1-r1