-
Notifications
You must be signed in to change notification settings - Fork 40
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
Default to high user ID #3277
Labels
breaking
Breaking change, requires major version bump
priority-2-important
User-visible bugs or very important features
status:in-progress
Someone is working on implementation
type:feature
Feature (new functionality)
Milestone
Comments
do you have a preference? |
Pick a random high number? |
i'll pick |
viceice
added a commit
that referenced
this issue
Sep 30, 2024
viceice
added a commit
that referenced
this issue
Sep 30, 2024
viceice
added
status:in-progress
Someone is working on implementation
type:feature
Feature (new functionality)
priority-2-important
User-visible bugs or very important features
labels
Oct 1, 2024
viceice
added a commit
that referenced
this issue
Oct 1, 2024
viceice
added a commit
that referenced
this issue
Oct 1, 2024
viceice
added a commit
that referenced
this issue
Oct 1, 2024
viceice
added a commit
that referenced
this issue
Oct 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking
Breaking change, requires major version bump
priority-2-important
User-visible bugs or very important features
status:in-progress
Someone is working on implementation
type:feature
Feature (new functionality)
Some security guides/scanners recommend running containers with a high user ID.
Refs:
Particularly, user 1000 is one of the most likely to have a conflict, but I think we can pick a really high one semi-randomly so that the chance a user needs to use it for something else already is close to zero.
The text was updated successfully, but these errors were encountered: