ci: lxc-trixie.yml, trixie in an unprivileged system container #17
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Keel-Linux/.github!17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ci/lxc-trixie"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds the reusable workflow
lxc-trixie.yml. It runs a repository's commands as root in a Debian trixie system container: an unprivileged LXC container with its own systemd, created from the download template on keel-lxc-1 by the runner user, with no sudo. It replaces everycontainer: debian:trixiejob in the organization (keel-core, common, anubis, libnginx-mod-http-coraza, coreruleset, libcoraza). Those PRs call it at@ci/lxc-trixieuntil this merges, then switch to@main.runorscript,systemd,backports,fetch-depth,download/download-dir,artifact-dir/artifact-name,timeout.systemd-run --user --scope, asbin/unprivileged-lxcdoes. The leftover tree is removed withunprivileged-lxc cleanup.pull_request_targetnever reach the runner. The job is skipped for them.build-deb.yml, which had no callers and neededsudo apt-get.<caller job> / trixie. No required check in the organization uses these jobs.Test plan