Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set user by id in Dockerfile #234

Open
juliangruendner opened this issue Nov 13, 2023 · 0 comments
Open

Set user by id in Dockerfile #234

juliangruendner opened this issue Nov 13, 2023 · 0 comments
Assignees

Comments

@juliangruendner
Copy link
Contributor

juliangruendner commented Nov 13, 2023

The user should be set by id in the Dockerfile like in our other projects.

Set user id to 10001

Example see: https://github.com/medizininformatik-initiative/flare/blob/main/Dockerfile

When changing the user ensure that all the functions of the Backend still work.

michael-82 added a commit that referenced this issue Nov 13, 2023
- do not create a new user "feasibility" with group but use user with id 10001 instead
- adapt check in github action
michael-82 added a commit that referenced this issue Nov 13, 2023
- do not create a new user "feasibility" with group but use user with id 10001 instead
- adapt check in github action
@michael-82 michael-82 linked a pull request Nov 13, 2023 that will close this issue
michael-82 added a commit that referenced this issue Nov 13, 2023
- do not create a new user "feasibility" with group but use user with id 10001 instead
- adapt check in github action
michael-82 added a commit that referenced this issue Nov 22, 2023
- do not create a new user "feasibility" with group but use user with id 10001 instead
- adapt check in github action
michael-82 added a commit that referenced this issue Jan 11, 2024
- do not create a new user "feasibility" with group but use user with id 10001 instead
- adapt check in github action
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants