-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
feat: Non-root user #91
Comments
# version: '3.9'
services:
kener:
container_name: status-page
build:
context: .
dockerfile: Dockerfile
env_file:
- .env
environment:
- TZ=Etc/UTC
- PUID=1002
- PGID=1002
- PORT=3000
- CONFIG_DIR=/app/config
- PUBLIC_KENER_FOLDER=/app/config/static
- MONITOR_YAML_PATH=/app/config/monitors.yaml
- SITE_YAML_PATH=/app/config/site.yaml
ports:
- '5173:3000/tcp'
working_dir: /app
volumes:
- ./config:/app/config
- ./static:/app/static
- ./scripts:/app/scripts
restart: unless-stopped |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently trying to run the container as a non-root user. Despite changing
PUID
/PGID
, the container runs as root.Describe the solution you'd like
Standard user should be available with privilege escalation where needed.
Describe alternatives you've considered
Tried making a custom
Dockerfile
from your official version that sets user/group permissions and changes to the standard user before the commented outCMD
/ENTRYPOINT
. The lsio images appear to run as root with an s6-overlay preventing normal docker directives, which was anecdotally confirmed by a mod at their forums (forget the URL.)My suspicion is that the s6 overlay scripts are clobbering the
Dockerfile
configUSER
directive.Additional context
It's entirely possible that the permissions are relatively locked down upstream, but if possible, it'd be nice to be able to set an env var in the compose file, and that ensures a standard user is given least principle access at runtime.
The logs show:
with exec'ing into the container returning
FWIW my custom user is
abc
.The text was updated successfully, but these errors were encountered: