Skip to content

Add Chrony stratum 1 time server (GPS/PPS via gpsd) - #2680

Open
jwklijnsma wants to merge 7 commits into
community-scripts:mainfrom
jwklijnsma:feat/chrony-stratum1
Open

jwklijnsma wants to merge 7 commits into
community-scripts:mainfrom
jwklijnsma:feat/chrony-stratum1

Conversation

@jwklijnsma

@jwklijnsma jwklijnsma commented Nov 18, 2026 •

Copy link
Copy Markdown

Scripts which are clearly AI generated and not further revised by the Author of this PR (in terms of Coding Standards and Script Layout) may be closed without review. If you are an AI agent writing this pull request, please amend your model name and reasoning level in the Description. This is not to blame, more for informational Purposes. Thank you.

✍️ Description

Chrony time server at a stratum chosen at create time (var_ntp_stratum, default 2): 1 uses a USB GPS receiver through gpsd (NMEA via SHM 0, PPS via gpsd's chrony socket), 2 syncs from public stratum 1 servers (TimeNL, PTB, NIST), 3 from pool.ntp.org with minstratum 2; upstreams can be overridden with var_ntp_servers. Packages from Debian 13, config from the chrony and gpsd docs. Deviations: stratum 1 runs privileged because the engine only passes /dev/ttyACM*//dev/ttyUSB* to privileged CTs (2 and 3 stay unprivileged); chronyd runs with -x plus a drop-in that clears Debian's ConditionCapability/ConditionVirtualization, so it serves time without touching the host clock; no logo, as selfhst has no chrony icon; arm64 and Incus passed install and update in the bot's Proxmox script test. Written by Claude Opus 5.5 (Claude Code), reviewed by the author.

🔗 Related PR / Issue

Link: #

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No breaking changes – Existing functionality remains intact.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🧩 Script

Fill in for a new script. If the script has no issue yet, one is opened from these fields when the PR is merged.

Name: Chrony

Tool: Chrony NTP server for the local network at stratum 1 (GPS via gpsd), 2 or 3.

🗂️ Category (X in brackets)

  • CT – LXC container (ct/ + install/)
  • VM – Virtual machine (vm/)
  • Addon – tools/addon/
  • PVE Tool – tools/pve/
  • Other – path given in the Description

🖥️ Platform – tested on (X in brackets)

  • Proxmox VE – Created on a Proxmox VE host and the app works.
  • Incus – Created on an Incus host and the app works.

Application containers run on both; tick what you actually tested. VMs and host tools are Proxmox only.

🏗️ Architecture (X in brackets)

  • arm64 supported - Tested and supported on arm64.
  • arm64 not tested - Assumed to work on arm64, but testing has not been done.
  • arm64 not supported - Confirmed upstream dependencies or binaries do not support arm64.

amd64 support is assumed.


🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • ✨ New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔍 Code & Security Review (X in brackets)

  • Follows CODE-AUDIT.md & CONTRIBUTING.md guidelines
  • Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
  • No hardcoded credentials
  • No Docker / Docker Compose – The application is installed bare-metal; Docker is not used.
  • No git pull – Updates use fetch_and_deploy_gh_release, fetch_and_deploy_codeberg_release, fetch_and_deploy_gl_release, or fetch_and_deploy_from_url instead of git pull.

📋 Additional Information (optional)


📦 Application Requirements (for new scripts)

⚠️ Do not remove this section.
It is used by automated PR validation checks.
If this PR is not a new script submission, leave the checkboxes unchecked.

Required for 🆕 New script submissions.
Pull requests that do not meet these requirements may be closed without review.

  • The application is at least 6 months old
  • The application is actively maintained
  • The application has 1,000+ GitHub stars
  • Official release tarballs are published
  • I understand that not all scripts will be accepted due to various reasons and criteria by the community-scripts ORG

🌐 Source

https://chrony-project.org/ · https://gitlab.com/chrony/chrony · https://gpsd.io/


🤖 AI Assistance (X in brackets)

If you used an AI tool (GitHub Copilot, Claude, ChatGPT, etc.) to write or generate any scripts in this PR, you must confirm compliance below.
Select exactly one option.

Please describe to which degree, if any, an LLM was used in creating this pull request. Name the model(s) used and, if applicable, the reasoning/thinking effort level (e.g. "Claude Sonnet 4.5, high reasoning, used to draft the install script, then manually reviewed and tested" or "No LLM used"). This is informational, not a penalty — but scripts that are clearly AI-generated and not further revised by the author to match CODE-AUDIT.md / CONTRIBUTING.md may be closed without review.

Claude Opus 5.5, standard reasoning, used to draft the ct, install and json files following CLAUDE.md, then reviewed by the author.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SZrFpmr3MyXvpLAxxcqUwU
@jwklijnsma
jwklijnsma requested a review from a team as a code owner November 18, 2026 17:37
@github-actions

Copy link
Copy Markdown
Contributor

👋 @jwklijnsma this PR adds new file(s) under ct/ or install/, but the 🆕 New script box in the Type of Change section isn't checked:

  • ct/chrony.sh
  • install/chrony-install.sh

If this is a new script submission, please check that box and fill out the 📦 Application Requirements section — it's required for review.
If this isn't actually a new script (e.g. a rename or a shared helper file), you can ignore this message.

@github-actions

github-actions Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

⚠️ Not ready for review yet

@jwklijnsma, this pull request is missing the following:

  • The application has 1,000+ GitHub stars

Edit the PR description to fix it — no new PR needed. This check runs again on every edit and clears itself once everything is in place.

Until then the PR is marked stale and will be closed in 7 days.


@community-scripts/contributor please take a look: close it, comment, or set keep-open to keep it.

@github-actions github-actions Bot added new script requirements missing PR description misses template items; closes after 7 days unless fixed or keep-open stale labels Nov 18, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Try this branch

The engine and the scripts resolve independently, so this runs the changed
ct/ and install/ scripts against the production engine:

export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/jwklijnsma/DevScripts/feat/chrony-stratum1
bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/chrony.sh")"

Both lines are needed. Without COMMUNITY_SCRIPTS_URL the engine falls back to
main, so curling the branch URL on its own gives you the ct/ script from
this PR and the install/ script from main. Frequently the one you meant to test.

The same command works on an Incus host: the engine detects the platform and
loads the matching backend, while the scripts still come from this branch.

Useful while testing

dev_mode=net logs every fetch with status and URL, which is the quickest way
to confirm the branch is really being used. dev_mode=keep stops a failed
build from deleting the container along with the evidence.

export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/jwklijnsma/DevScripts/feat/chrony-stratum1
dev_mode=net,keep bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/chrony.sh")"
Against a core branch as well

Add COMMUNITY_SCRIPTS_CORE_URL=https://raw.githubusercontent.com/OWNER/core/BRANCH
to test an engine change at the same time. The two resolve independently.

Stratum is chosen at create time (var_ntp_stratum). Stratum 2 syncs from
public stratum 1 servers, stratum 3 from the NTP pool with minstratum 2;
both run unprivileged. Upstream servers can be set with var_ntp_servers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SZrFpmr3MyXvpLAxxcqUwU

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Proxmox script test failed at 30ea8f2:

  • ct/chrony.sh (pve): update: exited 114: Not continuing: only 18% of / is free and there is nobody to ask.

Logs and details: test result. Push a fix, then ask for /test again.

@github-actions
github-actions Bot dismissed their stale review November 18, 2026 17:50

Replaced by a newer Proxmox script test.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Proxmox script test failed at 5ea53d3:

  • ct/chrony.sh (pve): update: exited 114: Not continuing: only 18% of / is free and there is nobody to ask.

Logs and details: test result. Push a fix, then ask for /test again.

- Raise the default disk to 4 GB; the pve update stopped at 82% of 2 GB
- update_script exits early when chrony/gpsd have no pending upgrade
- gpsd only starts when the GPS device exists (no journal errors without one)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SZrFpmr3MyXvpLAxxcqUwU
@github-actions
github-actions Bot dismissed their stale review November 18, 2026 18:13

Proxmox script test passed at 2410969.

@michelroegl-brunner michelroegl-brunner left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jwklijnsma This is clearly hard to track the requirements as it is hosted on gitlab, so the number of stars there to not alligne with github.
Do you have any way on giving us a source on how widley used this app is?

Otherwise we can not determine if we want to add this app or not.

Comment thread ct/chrony.sh Resolved
@jwklijnsma

Copy link
Copy Markdown
Author

@jwklijnsma This is clearly hard to track the requirements as it is hosted on gitlab, so the number of stars there to not alligne with github. Do you have any way on giving us a source on how widley used this app is?

Otherwise we can not determine if we want to add this app or not.

Thanks for taking a look! Fair point, the star count doesn’t work for chrony: development lives on GitLab and the GitHub copy is only a mirror. Usage is better shown by the distros and clouds that ship or recommend it:

Ubuntu: chrony has been the default time daemon since 25.10, replacing systemd-timesyncd, and 26.04 LTS ships it with NTS enabled. Docs: https://documentation.ubuntu.com/server/how-to/networking/chrony-client
RHEL (and so Rocky, Alma, CentOS Stream): chronyd has been the default NTP client since RHEL 8 replaced ntpd. https://www.redhat.com/en/blog/chrony-time-services-linux
AWS: Amazon’s Time Sync Service docs use chrony for Linux instances, and the launch post recommends chrony over ntpd. https://aws.amazon.com/blogs/aws/keeping-time-with-amazon-time-sync-service/
Debian: packaged in main and supported as an NTP server, which is how this script installs it.

So most Linux servers in the wild already run chrony as a client. This script adds the part that’s missing in a homelab: running it as a stratum 1 (GPS), 2 or 3 server for the local network.

jwklijnsma and others added 4 commits November 19, 2026 23:02
Both passed install and update in the Proxmox script test at 5ea53d3.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SZrFpmr3MyXvpLAxxcqUwU
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SZrFpmr3MyXvpLAxxcqUwU
Stratum 2 needs no GPS hardware and runs unprivileged; stratum 1 stays
available from the menu or with var_ntp_stratum=1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SZrFpmr3MyXvpLAxxcqUwU
@github-actions

Copy link
Copy Markdown
Contributor

Proxmox script test

@jwklijnsma ✅ 2/2 passed at 873b4d4

Script Platform Install Update Duration Detail
ct/chrony.sh pve ✅ ➖ 5m33s no URL to check; update: nothing to update (Chrony and gpsd are already up to date)
ct/chrony.sh incus ✅ ➖ 2m38s no URL to check; update: nothing to update (Chrony and gpsd are already up to date)
ct/chrony.sh arm64 ✅ ➖ 2m19s no URL to check; update: nothing to update (Chrony and gpsd are already up to date)

ARM64 (information only, not counted): 1/1 passed.

Notes (information only, not counted):

  • ct/chrony.sh (pve): 2 error line(s) in the journal since boot, e.g. Fatal error : adjtimex(0x8001) failed : Operation not permitted; Failed to start chrony.service - chrony, an NTP client/server.
  • ct/chrony.sh (incus): 2 error line(s) in the journal since boot, e.g. Fatal error : adjtimex(0x8001) failed : Operation not permitted; Failed to start chrony.service - chrony, an NTP client/server.
  • ct/chrony.sh (arm64): 2 error line(s) in the journal since boot, e.g. Fatal error : adjtimex(0x8001) failed : Operation not permitted; Failed to start chrony.service - chrony, an NTP client/server.
📊 Resources
Script Platform Usage
ct/chrony.sh pve disk 0.7 of 4 GB · RAM at rest 25 of 512 MB · OOM kills 0
ct/chrony.sh incus disk 0.5 of 4 GB · RAM at rest 21 of 512 MB · OOM kills 0
ct/chrony.sh arm64 disk 0.8 of 4 GB · RAM at rest 21 of 512 MB · OOM kills 0
📄 ct/chrony.sh (pve) — install log (963 lines)
… 587 earlier lines cut, the full log is in the run artifacts
Preparing to unpack .../libssl3t64_3.5.7-1~deb13u3_amd64.deb ...
Unpacking libssl3t64:amd64 (3.5.7-1~deb13u3) over (3.5.6-1~deb13u2) ...
Setting up libssl3t64:amd64 (3.5.7-1~deb13u3) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 20284 files and directories currently installed.)
Preparing to unpack .../libapt-pkg7.0_3.0.4_amd64.deb ...
Unpacking libapt-pkg7.0:amd64 (3.0.4) over (3.0.3) ...
Setting up libapt-pkg7.0:amd64 (3.0.4) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 20284 files and directories currently installed.)
Preparing to unpack .../archives/apt_3.0.4_amd64.deb ...
Unpacking apt (3.0.4) over (3.0.3) ...
Setting up apt (3.0.4) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 20284 files and directories currently installed.)
Preparing to unpack .../apt-utils_3.0.4_amd64.deb ...
Unpacking apt-utils (3.0.4) over (3.0.3) ...
Preparing to unpack .../libc-bin_2.41-12+deb13u4_amd64.deb ...
Unpacking libc-bin (2.41-12+deb13u4) over (2.41-12+deb13u3) ...
Setting up libc-bin (2.41-12+deb13u4) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 20284 files and directories currently installed.)
Preparing to unpack .../login_1%3a4.16.0-2+really2.41.5-0+deb13u1_amd64.deb ...
Unpacking login (1:4.16.0-2+really2.41.5-0+deb13u1) over (1:4.16.0-2+really2.41-5) ...
Preparing to unpack .../logsave_1.47.2-3+b12_amd64.deb ...
Unpacking logsave (1.47.2-3+b12) over (1.47.2-3+b11) ...
Preparing to unpack .../libext2fs2t64_1.47.2-3+b12_amd64.deb ...
Leaving 'diversion of /lib/x86_64-linux-gnu/libe2p.so.2 to /lib/x86_64-linux-gnu/libe2p.so.2.usr-is-merged by libext2fs2t64'
Leaving 'diversion of /lib/x86_64-linux-gnu/libe2p.so.2.3 to /lib/x86_64-linux-gnu/libe2p.so.2.3.usr-is-merged by libext2fs2t64'
Leaving 'diversion of /lib/x86_64-linux-gnu/libext2fs.so.2 to /lib/x86_64-linux-gnu/libext2fs.so.2.usr-is-merged by libext2fs2t64'
Leaving 'diversion of /lib/x86_64-linux-gnu/libext2fs.so.2.4 to /lib/x86_64-linux-gnu/libext2fs.so.2.4.usr-is-merged by libext2fs2t64'
Unpacking libext2fs2t64:amd64 (1.47.2-3+b12) over (1.47.2-3+b11) ...
Setting up libext2fs2t64:amd64 (1.47.2-3+b12) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 20286 files and directories currently installed.)
Preparing to unpack .../0-e2fsprogs_1.47.2-3+b12_amd64.deb ...
Unpacking e2fsprogs (1.47.2-3+b12) over (1.47.2-3+b11) ...
Preparing to unpack .../1-libexpat1_2.9.0-1~deb13u1_amd64.deb ...
Unpacking libexpat1:amd64 (2.9.0-1~deb13u1) over (2.7.1-2) ...
Preparing to unpack .../2-postfix_3.10.13-0+deb13u1_amd64.deb ...
Unpacking postfix (3.10.13-0+deb13u1) over (3.10.12-0+deb13u2) ...
Preparing to unpack .../3-python3.13_3.13.5-2+deb13u5_amd64.deb ...
Unpacking python3.13 (3.13.5-2+deb13u5) over (3.13.5-2+deb13u3) ...
Preparing to unpack .../4-libpython3.13-stdlib_3.13.5-2+deb13u5_amd64.deb ...
Unpacking libpython3.13-stdlib:amd64 (3.13.5-2+deb13u5) over (3.13.5-2+deb13u3) ...
Preparing to unpack .../5-python3.13-minimal_3.13.5-2+deb13u5_amd64.deb ...
Unpacking python3.13-minimal (3.13.5-2+deb13u5) over (3.13.5-2+deb13u3) ...
Preparing to unpack .../6-libpython3.13-minimal_3.13.5-2+deb13u5_amd64.deb ...
Unpacking libpython3.13-minimal:amd64 (3.13.5-2+deb13u5) over (3.13.5-2+deb13u3) ...
Preparing to unpack .../7-tzdata_2026f-0+deb13u1_all.deb ...
Unpacking tzdata (2026f-0+deb13u1) over (2026b-0+deb13u1) ...
Preparing to unpack .../8-libcap2_1%3a2.75-10+deb13u1+b3_amd64.deb ...
Unpacking libcap2:amd64 (1:2.75-10+deb13u1+b3) over (1:2.75-10+deb13u1+b1) ...
Setting up libcap2:amd64 (1:2.75-10+deb13u1+b3) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 20286 files and directories currently installed.)
Preparing to unpack .../libpcre2-8-0_10.46-1~deb13u3_amd64.deb ...
Unpacking libpcre2-8-0:amd64 (10.46-1~deb13u3) over (10.46-1~deb13u1) ...
Setting up libpcre2-8-0:amd64 (10.46-1~deb13u3) ...
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 20286 files and directories currently installed.)
Preparing to unpack .../00-dhcpcd-base_1%3a10.1.0-11+deb13u4_amd64.deb ...
Unpacking dhcpcd-base (1:10.1.0-11+deb13u4) over (1:10.1.0-11+deb13u3) ...
Preparing to unpack .../01-vim-tiny_2%3a9.1.1230-2+deb13u2_amd64.deb ...
Unpacking vim-tiny (2:9.1.1230-2+deb13u2) over (2:9.1.1230-2) ...
Preparing to unpack .../02-vim-common_2%3a9.1.1230-2+deb13u2_all.deb ...
Unpacking vim-common (2:9.1.1230-2+deb13u2) over (2:9.1.1230-2) ...
Preparing to unpack .../03-bind9-dnsutils_1%3a9.20.30-1~deb13u1_amd64.deb ...
Unpacking bind9-dnsutils (1:9.20.30-1~deb13u1) over (1:9.20.23-1~deb13u1) ...
Preparing to unpack .../04-bind9-host_1%3a9.20.30-1~deb13u1_amd64.deb ...
Unpacking bind9-host (1:9.20.30-1~deb13u1) over (1:9.20.23-1~deb13u1) ...
Preparing to unpack .../05-bind9-libs_1%3a9.20.30-1~deb13u1_amd64.deb ...
Unpacking bind9-libs:amd64 (1:9.20.30-1~deb13u1) over (1:9.20.23-1~deb13u1) ...
Preparing to unpack .../06-openssl_3.5.7-1~deb13u3_amd64.deb ...
Unpacking openssl (3.5.7-1~deb13u3) over (3.5.6-1~deb13u2) ...
Preparing to unpack .../07-ca-certificates_20250419+deb13u1_all.deb ...
Unpacking ca-certificates (20250419+deb13u1) over (20250419) ...
Preparing to unpack .../08-libc-l10n_2.41-12+deb13u4_all.deb ...
Unpacking libc-l10n (2.41-12+deb13u4) over (2.41-12+deb13u3) ...
Preparing to unpack .../09-locales_2.41-12+deb13u4_all.deb ...
Unpacking locales (2.41-12+deb13u4) over (2.41-12+deb13u3) ...
Preparing to unpack .../10-xz-utils_5.8.1-1+deb13u2_amd64.deb ...
Unpacking xz-utils (5.8.1-1+deb13u2) over (5.8.1-1+deb13u1) ...
Preparing to unpack .../11-libcap2-bin_1%3a2.75-10+deb13u1+b3_amd64.deb ...
Unpacking libcap2-bin (1:2.75-10+deb13u1+b3) over (1:2.75-10+deb13u1+b1) ...
Preparing to unpack .../12-libcom-err2_1.47.2-3+b12_amd64.deb ...
Unpacking libcom-err2:amd64 (1.47.2-3+b12) over (1.47.2-3+b11) ...
Preparing to unpack .../13-libss2_1.47.2-3+b12_amd64.deb ...
Unpacking libss2:amd64 (1.47.2-3+b12) over (1.47.2-3+b11) ...
Setting up libexpat1:amd64 (2.9.0-1~deb13u1) ...
Setting up libc-l10n (2.41-12+deb13u4) ...
Setting up apt-utils (3.0.4) ...
Setting up bsdextrautils (2.41.5-0+deb13u1) ...
Setting up bind9-libs:amd64 (1:9.20.30-1~deb13u1) ...
Setting up libcom-err2:amd64 (1.47.2-3+b12) ...
Setting up locales (2.41-12+deb13u4) ...
Generating locales (this might take a while)...
  C.UTF-8... done
  en_SC.UTF-8... done
  es_EC.UTF-8... done
Generation complete.
Setting up tzdata (2026f-0+deb13u1) ...
Current default time zone: 'Europe/Vienna'
Local time is now:      Thu Nov 19 23:15:12 CET 2026.
Universal Time is now:  Thu Nov 19 22:15:12 UTC 2026.
Run 'dpkg-reconfigure tzdata' if you wish to change it.
Setting up libcap2-bin (1:2.75-10+deb13u1+b3) ...
Setting up libpython3.13-minimal:amd64 (3.13.5-2+deb13u5) ...
Setting up vim-common (2:9.1.1230-2+deb13u2) ...
Setting up xz-utils (5.8.1-1+deb13u2) ...
Setting up libss2:amd64 (1.47.2-3+b12) ...
Setting up dhcpcd-base (1:10.1.0-11+deb13u4) ...
Setting up logsave (1.47.2-3+b12) ...
Setting up libfdisk1:amd64 (2.41.5-0+deb13u1) ...
Setting up postfix (3.10.13-0+deb13u1) ...
Postfix (main.cf) configuration was not modified by debconf.  If you need to 
make changes, edit /etc/postfix/main.cf (and others) as needed.  To view 
Postfix configuration values, see postconf(1).
After modifying main.cf, be sure to run 'systemctl reload postfix'.
Setting up mount (2.41.5-0+deb13u1) ...
Setting up perl-modules-5.40 (5.40.1-6+deb13u1) ...
Setting up python3.13-minimal (3.13.5-2+deb13u5) ...
Setting up bind9-host (1:9.20.30-1~deb13u1) ...
Setting up openssl (3.5.7-1~deb13u3) ...
Setting up libpython3.13-stdlib:amd64 (3.13.5-2+deb13u5) ...
Setting up util-linux-extra (2.41.5-0+deb13u1) ...
Setting up login (1:4.16.0-2+really2.41.5-0+deb13u1) ...
Setting up python3.13 (3.13.5-2+deb13u5) ...
Setting up e2fsprogs (1.47.2-3+b12) ...
Setting up vim-tiny (2:9.1.1230-2+deb13u2) ...
Setting up fdisk (2.41.5-0+deb13u1) ...
Setting up libperl5.40:amd64 (5.40.1-6+deb13u1) ...
Setting up ca-certificates (20250419+deb13u1) ...
Updating certificates in /etc/ssl/certs...
rehash: warning: skipping ca-certificates.crt, it does not contain exactly one certificate or CRL
0 added, 2 removed; done.
Setting up perl (5.40.1-6+deb13u1) ...
Setting up bind9-dnsutils (1:9.20.30-1~deb13u1) ...
Processing triggers for libc-bin (2.41-12+deb13u4) ...
Processing triggers for systemd (257.13-1~deb13u1) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for debianutils (5.23.2) ...
Processing triggers for mailcap (3.74) ...
Processing triggers for postfix (3.10.13-0+deb13u1) ...
Restarting postfix
Processing triggers for ca-certificates (20250419+deb13u1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
[2026-11-19 23:15:28] [OK] Updated Container OS
[2026-11-19 23:15:28] [INFO] Installing Chrony
Reading package lists...
Building dependency tree...
Reading state information...
Installing:
  chrony
Suggested packages:
  networkd-dispatcher
REMOVING:
  systemd-timesyncd
Summary:
  Upgrading: 0, Installing: 1, Removing: 1, Not Upgrading: 0
  Download size: 310 kB
  Space needed: 497 kB / 3034 MB available
Get:1 http://deb.debian.org/debian trixie/main amd64 chrony amd64 4.6.1-3+deb13u2 [310 kB]
Fetched 310 kB in 0s (843 kB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 20284 files and directories currently installed.)
Removing systemd-timesyncd (257.13-1~deb13u1) ...
Selecting previously unselected package chrony.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 20263 files and directories currently installed.)
Preparing to unpack .../chrony_4.6.1-3+deb13u2_amd64.deb ...
Unpacking chrony (4.6.1-3+deb13u2) ...
Setting up chrony (4.6.1-3+deb13u2) ...
Creating config file /etc/chrony/chrony.conf with new version
Creating config file /etc/chrony/chrony.keys with new version
dpkg-statoverride: warning: --update given but /var/log/chrony does not exist
Created symlink '/etc/systemd/system/chronyd.service' → '/usr/lib/systemd/system/chrony.service'.
Created symlink '/etc/systemd/system/multi-user.target.wants/chrony.service' → '/usr/lib/systemd/system/chrony.service'.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 148.
Processing triggers for dbus (1.16.2-2) ...
Processing triggers for man-db (2.13.1-1) ...
[2026-11-19 23:15:38] [OK] Installed Chrony
[2026-11-19 23:15:38] [INFO] Configuring Chrony as stratum 2
[2026-11-19 23:15:38] [OK] Configured Chrony as stratum 2
[2026-11-19 23:15:38] [INFO] Customizing Container
[2026-11-19 23:15:39] [OK] Customized Container
[2026-11-19 23:15:39] [INFO] Cleaning up
Reading package lists...
Building dependency tree...
Reading state information...
Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
[2026-11-19 23:15:40] [OK] Cleaned
🔄 ct/chrony.sh (pve) — update log (22 lines)
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
   ______                                      _ __           _____           _       __
  / ____/___  ____ ___  ____ ___  __  ______  (_) /___  __   / ___/__________(_)___  / /______
 / /   / __ \/ __ `__ \/ __ `__ \/ / / / __ \/ / __/ / / /   \__ \/ ___/ ___/ / __ \/ __/ ___/
/ /___/ /_/ / / / / / / / / / / / /_/ / / / / / /_/ /_/ /   ___/ / /__/ /  / / /_/ / /_(__  )
\____/\____/_/ /_/ /_/_/ /_/ /_/\__,_/_/ /_/_/\__/\__, /   /____/\___/_/  /_/ .___/\__/____/
                                                 /____/                    /_/
  Chrony
curl: (22) The requested URL returned error: 404
curl: (22) The requested URL returned error: 404
   ______                                      _ __           _____           _       __
  / ____/___  ____ ___  ____ ___  __  ______  (_) /___  __   / ___/__________(_)___  / /______
 / /   / __ \/ __ `__ \/ __ `__ \/ / / / __ \/ / __/ / / /   \__ \/ ___/ ___/ / __ \/ __/ ___/
/ /___/ /_/ / / / / / / / / / / / /_/ / / / / / /_/ /_/ /   ___/ / /__/ /  / / /_/ / /_(__  )
\____/\____/_/ /_/ /_/_/ /_/ /_/\__,_/_/ /_/_/\__/\__, /   /____/\___/_/  /_/ .___/\__/____/
                                                 /____/                    /_/
  Chrony
/dev/shm/cs-engine.AhBdSv/core/core.func: line 2711: /tmp/create-lxc-2ec3db39.log: No such file or directory
  ✔️  Chrony and gpsd are already up to date
  ⏳   Cleaning up
  ✔️  Cleaned
📄 ct/chrony.sh (incus) — install log (94 lines)
[2026-11-19 23:11:27] [INFO] Setting up Container OS
[2026-11-19 23:11:28] [OK] Set up Container OS
[2026-11-19 23:11:28] [OK] Network Connected: 10.98.0.55
[2026-11-19 23:11:29] [OK] IPv4 Internet Connected
[2026-11-19 23:11:29] No IPv6 Internet (IPv4 is enough)
[2026-11-19 23:11:29] [OK] Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ )
[2026-11-19 23:11:29] [INFO] Updating Container OS
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://deb.debian.org/debian-security trixie-security InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[2026-11-19 23:11:31] [OK] Updated Container OS
[2026-11-19 23:11:31] [INFO] Installing Chrony
Reading package lists...
Building dependency tree...
Reading state information...
Installing:
  chrony
Installing dependencies:
  libtext-charwidth-perl  libtext-wrapi18n-perl  ucf
Suggested packages:
  dnsutils  networkd-dispatcher
Summary:
  Upgrading: 0, Installing: 4, Removing: 0, Not Upgrading: 0
  Download size: 371 kB
  Space needed: 926 kB / 146 GB available
Get:1 http://deb.debian.org/debian trixie/main amd64 libtext-charwidth-perl amd64 0.04-11+b4 [9476 B]
Get:2 http://deb.debian.org/debian trixie/main amd64 libtext-wrapi18n-perl all 0.06-10 [8808 B]
Get:3 http://deb.debian.org/debian trixie/main amd64 ucf all 3.0052 [43.3 kB]
Get:4 http://deb.debian.org/debian trixie/main amd64 chrony amd64 4.6.1-3+deb13u2 [310 kB]
Preconfiguring packages ...
Fetched 371 kB in 1s (298 kB/s)
Selecting previously unselected package libtext-charwidth-perl:amd64.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 16513 files and directories currently installed.)
Preparing to unpack .../libtext-charwidth-perl_0.04-11+b4_amd64.deb ...
Unpacking libtext-charwidth-perl:amd64 (0.04-11+b4) ...
Selecting previously unselected package libtext-wrapi18n-perl.
Preparing to unpack .../libtext-wrapi18n-perl_0.06-10_all.deb ...
Unpacking libtext-wrapi18n-perl (0.06-10) ...
Selecting previously unselected package ucf.
Preparing to unpack .../archives/ucf_3.0052_all.deb ...
Moving old data out of the way
Unpacking ucf (3.0052) ...
Selecting previously unselected package chrony.
Preparing to unpack .../chrony_4.6.1-3+deb13u2_amd64.deb ...
Unpacking chrony (4.6.1-3+deb13u2) ...
Setting up libtext-charwidth-perl:amd64 (0.04-11+b4) ...
Setting up libtext-wrapi18n-perl (0.06-10) ...
Setting up ucf (3.0052) ...
Setting up chrony (4.6.1-3+deb13u2) ...
Creating config file /etc/chrony/chrony.conf with new version
Creating config file /etc/chrony/chrony.keys with new version
dpkg-statoverride: warning: --update given but /var/log/chrony does not exist
Created symlink '/etc/systemd/system/chronyd.service' → '/usr/lib/systemd/system/chrony.service'.
Created symlink '/etc/systemd/system/multi-user.target.wants/chrony.service' → '/usr/lib/systemd/system/chrony.service'.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 148.
[2026-11-19 23:11:38] [OK] Installed Chrony
[2026-11-19 23:11:38] [INFO] Configuring Chrony as stratum 2
[2026-11-19 23:11:38] [OK] Configured Chrony as stratum 2
[2026-11-19 23:11:38] [INFO] Customizing Container
[2026-11-19 23:11:40] [OK] Customized Container
[2026-11-19 23:11:40] [INFO] Cleaning up
Reading package lists...
Building dependency tree...
Reading state information...
Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
[2026-11-19 23:11:41] [OK] Cleaned
🔄 ct/chrony.sh (incus) — update log (16 lines)
   ______                                      _ __           _____           _       __
  / ____/___  ____ ___  ____ ___  __  ______  (_) /___  __   / ___/__________(_)___  / /______
 / /   / __ \/ __ `__ \/ __ `__ \/ / / / __ \/ / __/ / / /   \__ \/ ___/ ___/ / __ \/ __/ ___/
/ /___/ /_/ / / / / / / / / / / / /_/ / / / / / /_/ /_/ /   ___/ / /__/ /  / / /_/ / /_(__  )
\____/\____/_/ /_/ /_/_/ /_/ /_/\__,_/_/ /_/_/\__/\__, /   /____/\___/_/  /_/ .___/\__/____/
                                                 /____/                    /_/
  Chrony
10.98.0.55
   ______                                      _ __           _____           _       __
  / ____/___  ____ ___  ____ ___  __  ______  (_) /___  __   / ___/__________(_)___  / /______
 / /   / __ \/ __ `__ \/ __ `__ \/ / / / __ \/ / __/ / / /   \__ \/ ___/ ___/ / __ \/ __/ ___/
/ /___/ /_/ / / / / / / / / / / / /_/ / / / / / /_/ /_/ /   ___/ / /__/ /  / / /_/ / /_(__  )
\____/\____/_/ /_/ /_/_/ /_/ /_/\__,_/_/ /_/_/\__/\__, /   /____/\___/_/  /_/ .___/\__/____/
                                                 /____/                    /_/
  Chrony
  ✔️  Chrony and gpsd are already up to date
📄 ct/chrony.sh (arm64) — install log (75 lines)
[2026-11-19 22:14:29] [INFO] Setting up Container OS
[2026-11-19 22:14:29] [OK] Set up Container OS
[2026-11-19 22:14:29] [OK] Network Connected: 10.98.0.212
[2026-11-19 22:14:33] [OK] IPv4 Internet Connected (TCP reachable; ICMP is filtered)
[2026-11-19 22:14:33] No IPv6 Internet (IPv4 is enough)
[2026-11-19 22:14:33] [OK] Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ )
[2026-11-19 22:14:34] [INFO] Updating Container OS
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://deb.debian.org/debian-security trixie-security InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[2026-11-19 22:14:35] [OK] Updated Container OS
[2026-11-19 22:14:35] [INFO] Installing Chrony
Reading package lists...
Building dependency tree...
Reading state information...
Installing:
  chrony
Suggested packages:
  dnsutils  networkd-dispatcher
Summary:
  Upgrading: 0, Installing: 1, Removing: 0, Not Upgrading: 0
  Download size: 300 kB
  Space needed: 778 kB / 110 GB available
Get:1 http://deb.debian.org/debian trixie/main arm64 chrony arm64 4.6.1-3+deb13u2 [300 kB]
Fetched 300 kB in 0s (3373 kB/s)
Selecting previously unselected package chrony.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 26675 files and directories currently installed.)
Preparing to unpack .../chrony_4.6.1-3+deb13u2_arm64.deb ...
Unpacking chrony (4.6.1-3+deb13u2) ...
Setting up chrony (4.6.1-3+deb13u2) ...
Creating config file /etc/chrony/chrony.conf with new version
Creating config file /etc/chrony/chrony.keys with new version
dpkg-statoverride: warning: --update given but /var/log/chrony does not exist
Created symlink '/etc/systemd/system/chronyd.service' → '/usr/lib/systemd/system/chrony.service'.
Created symlink '/etc/systemd/system/multi-user.target.wants/chrony.service' → '/usr/lib/systemd/system/chrony.service'.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 148.
[2026-11-19 22:14:37] [OK] Installed Chrony
[2026-11-19 22:14:37] [INFO] Configuring Chrony as stratum 2
[2026-11-19 22:14:37] [OK] Configured Chrony as stratum 2
[2026-11-19 22:14:37] [INFO] Customizing Container
[2026-11-19 22:14:38] [OK] Customized Container
[2026-11-19 22:14:38] [INFO] Cleaning up
Reading package lists...
Building dependency tree...
Reading state information...
Summary:
  Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
[2026-11-19 22:14:39] [OK] Cleaned
🔄 ct/chrony.sh (arm64) — update log (16 lines)
   ______                                      _ __           _____           _       __
  / ____/___  ____ ___  ____ ___  __  ______  (_) /___  __   / ___/__________(_)___  / /______
 / /   / __ \/ __ `__ \/ __ `__ \/ / / / __ \/ / __/ / / /   \__ \/ ___/ ___/ / __ \/ __/ ___/
/ /___/ /_/ / / / / / / / / / / / /_/ / / / / / /_/ /_/ /   ___/ / /__/ /  / / /_/ / /_(__  )
\____/\____/_/ /_/ /_/_/ /_/ /_/\__,_/_/ /_/_/\__/\__, /   /____/\___/_/  /_/ .___/\__/____/
                                                 /____/                    /_/
  Chrony
10.98.0.212
   ______                                      _ __           _____           _       __
  / ____/___  ____ ___  ____ ___  __  ______  (_) /___  __   / ___/__________(_)___  / /______
 / /   / __ \/ __ `__ \/ __ `__ \/ / / / __ \/ / __/ / / /   \__ \/ ___/ ___/ / __ \/ __/ ___/
/ /___/ /_/ / / / / / / / / / / / /_/ / / / / / /_/ /_/ /   ___/ / /__/ /  / / /_/ / /_(__  )
\____/\____/_/ /_/ /_/_/ /_/ /_/\__,_/_/ /_/_/\__/\__, /   /____/\___/_/  /_/ .___/\__/____/
                                                 /____/                    /_/
  Chrony
  ✔️  Chrony and gpsd are already up to date

Full logs: workflow run (artifacts result-*). Comment /test to build again.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

keep-open new script requirements missing PR description misses template items; closes after 7 days unless fixed or keep-open

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants