Add support for rootless image #129
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
4 Participants
Notifications
Total Time Spent: 4 hours
Due Date
Starefossen
4 hours
No due date set.
Dependencies
No dependencies set.
Reference: gitea/helm-chart#129
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "Starefossen/helm-chart:rootless"
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 pull request adds rootless support that has been introduced in the upcoming v1.14 version (
latest-rootless
tag). The rootless image is a requirement for running as an non-root user which is reccomended best practice – even inside contaienrs.The changes here are based on the discussion in #115.
? There are some differences with default variables in the two images which presents some challenges with supporting both.
Tasks
image.rootless
boolean option-rootles
suffixsu git
in init script when running rootlessa3b9c2531b
toa6dde4f4f3
cb536708a0
to93390c3693
WIP: Add support for rootless imageto Add support for rootless imageThis is ready for review. I am currently running this for my installation.
Thanks, I will try this on my new install. Can you rebase the PR ?
d163eb0463
tod549cc675a
@sapk rebased, I have running this in production since I opened the PR. Working great so far ?
Yes this seems good. It would jsut need to add the rootless value to the README.md to indicate it but it can be done later since by default false.
I had to move the
gitea-repositories
inside the pvc to migrate from an non-rootless image.This should be a common path rewrite with any docker rootless migration since path were pretty bad before. This comment is just if someone encounter the same problem.
Hi there, sorry for the late response. I will fokus on this PR this week.
Currently getting Error 500 on existing repositories when upgrading.
I'm looking into this issue
@ -27,12 +27,12 @@ stringData:
{{- $_ := set .Values.gitea.config "security" dict -}}
{{- end -}}
In order to migrate from pre 1.14 to 1.14 we need this in config.yaml
@Starefossen please rebase and add the suggested lines into config.yaml :)
Readding change request
@Starefossen any news on when you can back to this commit and do the changes, so we can merge it ?
Looking forward to this upgrade, do you guys have any ETA on this?
@Dunky13 IF Starefossen will not reply until tomorrow i will cherry-pick all pending changes into a single branch from the currently open PRs and prepare an update
now included in #148
Pull request closed