fix: user id 2 allowed uid range in dockerfiles and deployment files. #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request updates the user ID used for running application containers and deployments from
65532
to10001
across several services and infrastructure templates. This change helps ensure consistency and avoids warning that the user id is out of range (min/max ID)Container user ID standardization:
RUN adduser
command in the Dockerfiles foradmin-backend
,document-extractor
,mcp-server
, andrag-backend
services to use UID10001
instead of65532
. [1] [2] [3] [4]Kubernetes deployment configuration:
runAsUser
value in thesecurityContext
of the deployment templates foradmin-backend
,backend
, andextractor
to10001
instead of65532
. [1] [2] [3]