gitea/helm-gitea
Fork 169
Code Issues 53 Pull Requests 11 Actions Releases 103 Activity

Want to run with security context #120

New Issue
Closed
opened 2021-02-22 16:46:40 +00:00 by Dunky13 · 1 comment
Dunky13 commented 2021-02-22 16:46:40 +00:00
Contributor
Copy Link

When running this application with a security context where the gitea pod is not allowed to run as a root user, it does not get full gitea access, as the docker image is build on root access, and the entrypoint does some root/user-id magic to make it work.

Is it possible to get the helm chart updated to allow non-root securityContext. As the init container requires root, and the gitea container seems to need is, but why?

When running this application with a security context where the gitea pod is not allowed to run as a root user, it does not get full gitea access, as the docker image is build on root access, and the entrypoint does some root/user-id magic to make it work. Is it possible to get the helm chart updated to allow non-root securityContext. As the `init` container requires root, and the `gitea` container seems to need is, but why?
techknowlogick commented 2021-02-22 18:29:48 +00:00
Owner
Copy Link

There is also a rootless version of the gitea container that you could try using.

Root is used in standard container due to historical reasons of packaging opensshd which bound to a port that needed root permissions, as we didn't want to create a breaking change that is why we now also offer the rootless version.

There is also a rootless version of the gitea container that you could try using. Root is used in standard container due to historical reasons of packaging opensshd which bound to a port that needed root permissions, as we didn't want to create a breaking change that is why we now also offer the rootless version.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
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
workaround
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
42wim 6543 a1012112796 Akkuman appleboy axifive betacat0 blumia bwko caicandong ChristopherHX DaanSelen davidsvantesson delvh denyskon fuxiaohei gary-kim garymoon giteabot guillep2k HesterG hiifong jaqra jolheiser jonasfranz jpraet kdumontnu kemzeb kerwin612 khmarbaise KN4CK3R kolaente lafriks lng2020 lotherk luhahn lunny mrsdizzie noerw pat-s puni9869 renovate-bot richmahn rossigee sapk screenshots sillyguodong silverwind smartclip_tim strk tboerger techknowlogick TheFox0x7 tobiasbp typeless volker.raschek wolfogre wxiaoguang yardenshoham yp05327 zeripath Zettat123
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: gitea/helm-gitea#120
No description provided.
Delete Branch "%!s()"

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?