Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

[Feature Request] Only chown /data when not already owned? #945

Copy link
Copy link
@RMHogervorst

Description

@RMHogervorst
Issue body actions

First off, this project is really nice, and man what a lovely UI!

Is your feature request related to a problem? Please describe.

The container runs as 1000:1000 and that is great, but during startup it tries to chown /data. Which is a privileged action. I hope this is not necessary, and can be toggled or first checked before executing?

Describe the solution you'd like
I could run an init container that chowns 1000:1000 /data and than the container could run everything unprivileged. I also understand that chowning the volume is necessary for docker compose with an external volume (and ease of use). Could you make it switch or something? or first check if the rights are correct before running chown?

Describe alternatives you've considered
I have tried an init container but the reitti container still tries to chown.

Additional context
I'm running the container 'dedicatedcode/reitti' version: '4.0' (in kubernetes), based on the docker compose file.

Possibly related to #688

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.