Repository navigation
Nightly security updates on the server, and how to update Docker, containerd and the kernel by hand - #114
Merged
Conversation
…tainerd and the kernel by hand Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The server had no automatic updates: Amazon Linux 2023 stays on the release it booted from (2026-09-18 here), and 66 security fixes had piled up.
What changes
infra/napoland.yaml: the first boot turns ondnf-automaticfor security updates every night (around 06:00 UTC), from the latest Amazon Linux release. Docker, containerd, runc and the kernel are left out, because they restart every container or need a reboot.docs/OPERATIONS.md: a "Server updates" section with the nightly runs and the by-hand update of those four (snapshots and a dump first, update, reboot, checks, and what to do if something does not come back). Also a note that a first-boot change stops and starts the server when deployed, and does not run again on it.Already live on the server (2026-10-23, done by hand through SSM)
So this change only matters for a new server.
Checks
npm run checkpasses.aws cloudformation validate-template.bash -n.Deploying
aws cloudformation deploy, as in OPERATIONS.md) stops and starts the server for a minute or two, without running the first boot again. Its settings are already in place, so it can wait for a quiet moment.Claude Code wrote all of this at the owner's request, and a person has not read it yet.
🤖 Generated with Claude Code