refactor: run container as root, remove sudo#821
Merged
Conversation
Remove the non-root perstack user and sudo package from the container. Users who need a non-root setup can use perstack/perstack as a base image and add their own user with apt-get install. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
perstackuser andsudopackage from Docker imageperstack/perstackas base imagesudofromapt-get installinstructionMotivation
The only reason for sudo was
apt-get install. Running as root simplifies the image and avoids unnecessary attack surface from the sudo binary itself. Users who need non-root isolation can add their own user in a derived Dockerfile.Test plan
🤖 Generated with Claude Code