document that the runner uses an instance-scoped registration token
record the failed bootstrap finding in the changelog
Why
The official chart marks DinD privileged in both modes. On this Ubuntu node, rootlesskit is still rejected by kernel.apparmor_restrict_unprivileged_userns, so rootless mode does not start unless the host-wide policy is weakened.
Validation
yamllint
helm lint against actions 0.1.1
helm template piped to kubectl apply --dry-run=client
rendered image and socket paths inspected
git diff --check
no Terraform state or plan files in the diff
Deployment
The initial release is currently pending with the old rootless DinD init container in CrashLoopBackOff. After merge, rerun helm upgrade with the reviewed values and verify runner registration plus the queued workflow.
## Summary
- switch the Gitea Actions sidecar from rootless DinD to regular DinD
- keep AppArmor's host-wide unprivileged-userns restriction enabled
- document that the runner uses an instance-scoped registration token
- record the failed bootstrap finding in the changelog
## Why
The official chart marks DinD privileged in both modes. On this Ubuntu node, rootlesskit is still rejected by kernel.apparmor_restrict_unprivileged_userns, so rootless mode does not start unless the host-wide policy is weakened.
## Validation
- yamllint
- helm lint against actions 0.1.1
- helm template piped to kubectl apply --dry-run=client
- rendered image and socket paths inspected
- git diff --check
- no Terraform state or plan files in the diff
## Deployment
The initial release is currently pending with the old rootless DinD init container in CrashLoopBackOff. After merge, rerun helm upgrade with the reviewed values and verify runner registration plus the queued workflow.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Why
The official chart marks DinD privileged in both modes. On this Ubuntu node, rootlesskit is still rejected by kernel.apparmor_restrict_unprivileged_userns, so rootless mode does not start unless the host-wide policy is weakened.
Validation
Deployment
The initial release is currently pending with the old rootless DinD init container in CrashLoopBackOff. After merge, rerun helm upgrade with the reviewed values and verify runner registration plus the queued workflow.