Fix ssh permission denied(publickey) at reinstalling the chart without deleting pvc #25
No reviewers
Labels
No Label
has
backport
in progress
invalid
kind
breaking
kind
bug
kind
build
kind
dependency
kind
deployment
kind
docs
kind
enhancement
kind
feature
kind
lint
kind
proposal
kind
question
kind
refactor
kind
security
kind
testing
kind
translation
kind
ui
need
backport
priority
critical
priority
low
priority
maybe
priority
medium
reviewed
duplicate
reviewed
invalid
reviewed
wontfix
skip-changelog
status
blocked
status
needs-feedback
status
needs-reviews
status
wip
upstream
gitea
upstream
other
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#25
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "luhahn/helm-chart: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?
Found a bug / strange behavior with longhorn storage. When gitea is reinstalled without deleting the PVC then kubernetes remounts the volume but uses default permissions for /data/git/.ssh which causes all ssh clone attempts to fail with: Permission denied (publickey)
The init container now creates this folder and sets permissions 700
@ -26,2 +26,4 @@
- name: SCRIPT
value: &script |-
mkdir -p /data/git/.ssh
chmod 700 /data/git/.ssh
Should this be recursive chmod, in case there are any existing files inside that folder already?
Somehow this only affects the main .ssh folder. I tried it manually with this command and everything works fine again after chmod 700 /data/git/.ssh even if there are files present already.
ah ok. thanks for testing :)