rootless image migration plans #8889

Closed
opened 2025-11-02 08:22:10 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @dkanada on GitHub (Apr 30, 2022).

Feature Description

Just curious if there were still plans to use the rootless image by default at some point as mentioned in #10154 last year. Seems like a year might be good enough to make the switch, but if that idea was dropped then feel free to disregard this suggestion.

Screenshots

No response

Originally created by @dkanada on GitHub (Apr 30, 2022). ### Feature Description Just curious if there were still plans to use the rootless image by default at some point as mentioned in #10154 last year. Seems like a year might be good enough to make the switch, but if that idea was dropped then feel free to disregard this suggestion. ### Screenshots _No response_
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 08:22:10 -06:00
Author
Owner

@wxiaoguang commented on GitHub (Apr 30, 2022):

I would suggest not use rootless at the moment, due to the builtin ssh server key exchange bug (from upstream).

@wxiaoguang commented on GitHub (Apr 30, 2022): I would suggest not use rootless at the moment, due to the builtin ssh server key exchange bug (from upstream). * https://github.com/go-gitea/gitea/issues/17910 * https://github.com/go-gitea/gitea/issues/17798
Author
Owner

@techknowlogick commented on GitHub (Apr 30, 2022):

Closing as the rootful image is still rather popular and the user support load from switching to rootless would be rather significant.

@techknowlogick commented on GitHub (Apr 30, 2022): Closing as the rootful image is still rather popular and the user support load from switching to rootless would be rather significant.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#8889