SSH not working due missing security capability in CRI-O environment #176
Reference in New Issue
Block a user
No description provided.
Delete Branch "master"
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?
This patch add the SYS_CHROOT capability if the securityContext is
undefined. Otherwise the SSH Server does not work correctly as described
in the issue #161.
Fixes: #161
WIP as per https://gitea.com/gitea/helm-chart/issues/161#issuecomment-440630
(in values.yaml)
Is
SYS_CHROOT
necessary for both image variants? If so, could you pleass extend this comment so that users don't get confused?Maybe something like
...except for clusters using cri-o where SYS_CHROOT needs to be set
. ?@volker.raschek Please update your branch to the latest master and have a look at that comment.
LGTM. Thanks for your effort.