authentik: scope blueprints chown to avoid recursing into the mp0 bind mount - #17008
Conversation
Try this branchThe engine and the scripts resolve independently, so this runs the changed export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/community-scripts/ProxmoxVE/fix-authentik-update-chown-bind-mount-lost-found
bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/authentik.sh")"Both lines are needed. Each script pins The same command works on an Incus host: the engine detects the platform and Useful while testing
export COMMUNITY_SCRIPTS_URL=https://raw.githubusercontent.com/community-scripts/ProxmoxVE/fix-authentik-update-chown-bind-mount-lost-found
dev_mode=net,keep bash -c "$(curl -fsSL "$COMMUNITY_SCRIPTS_URL/ct/authentik.sh")" |
|
approved by user; #16985 (comment) |
|
In line 231, it is not enough to just set the owner of the blueprints folder, the owner of all subfolders must be changed, however, the lost+found folder created when mounting volume 2 in the container is owned by nobody:nogroup and cannot be modified from the container, which is what causes the problem. |
thieneret
left a comment
There was a problem hiding this comment.
I tested it several times, it worked with find.
Meanwhile I found another error in the two sed lines.
Co-authored-by: thieneret <123479547+thieneret@users.noreply.github.com>
Co-authored-by: thieneret <123479547+thieneret@users.noreply.github.com>
Co-authored-by: thieneret <123479547+thieneret@users.noreply.github.com>
Co-authored-by: thieneret <123479547+thieneret@users.noreply.github.com>
Co-authored-by: thieneret <123479547+thieneret@users.noreply.github.com>
✍️ Description
should solve the issue, but i let the user test
🔗 Related Issue
Fixes #
✅ Prerequisites (X in brackets)
🤖 AI Assistance (X in brackets)
AGENTS.mdand.github/agents/pve-script-creator.agent.mdas guidance, and the output has been reviewed and corrected to match those guidelines.🛠️ Type of Change (X in brackets)
README,AppName.md,CONTRIBUTING.md, or other docs.💥 Breaking Change Advisory (only if you checked "Breaking change")
If this PR changes existing behaviour in a way that may require action before an
update, add a
breaking-changeadvisory block to this PR body. The website andthe in-container update guard read it to tell operators exactly what to expect,
what to do first, and — with
action: block— to stop an update until it'shandled. Every field is optional; the advisory auto-expires 30 days after merge.
Copy the block out of the comment below, fill it in, and paste it here: