Allow chroot directory to pre-exist for volume mount support#3967
Merged
Allow chroot directory to pre-exist for volume mount support#3967
Conversation
rockwotj
approved these changes
Feb 5, 2026
The chroot setup previously required the chroot directory to not exist, which prevented mounting ConfigMaps or other volumes directly inside the chroot path. This is a problem because the chroot-passthrough mechanism copies files (losing symlinks), which breaks fsnotify-based hot reload of authorization policy files mounted from ConfigMaps. Allow the chroot directory to pre-exist so that Kubernetes volume mounts can place files directly inside it. Also handle EROFS errors in the makeReadOnly step, since read-only volume mounts (like ConfigMaps) cannot be chmod'd. Pre-create /tmp/chroot in the cloud Dockerfile owned by the connect user so the process can populate the rest of the chroot structure at runtime.
birdayz
force-pushed
the
jb/chroot-volume-mount-support
branch
from
0acb24d to
b1ad35b
Compare
Contributor
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
2 participants
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 chroot setup previously required the chroot directory to not exist, which prevented mounting ConfigMaps or other volumes directly inside the chroot path. This is a problem because the chroot-passthrough mechanism copies files (losing symlinks), which breaks fsnotify-based hot reload of authorization policy files mounted from ConfigMaps.
Allow the chroot directory to pre-exist so that Kubernetes volume mounts can place files directly inside it. Also handle EROFS errors in the makeReadOnly step, since read-only volume mounts (like ConfigMaps) cannot be chmod'd.
Pre-create /tmp/chroot in the cloud Dockerfile owned by the connect user so the process can populate the rest of the chroot structure at runtime.
Add integration tests covering hierarchical authz scope matching with production-like resource names and policy bindings.