umputun / docker-logger

79%

LAST BUILD ON BRANCH master

branch: master

CHANGE BRANCH

x

Reset

• master
• HEAD
• code-review-fixes
• dependabot/github_actions/github-actions-updates-a2e7793ad6
• dependabot/go_modules/github.com/docker/docker-26.1.4incompatible
• dependabot/go_modules/github.com/docker/docker-27.1.0incompatible
• dependabot/go_modules/github.com/docker/docker-28.0.0incompatible
• dependabot/go_modules/github.com/go-pkgz/lgr-0.12.0
• dependabot/go_modules/github.com/moby/moby/v2-2.0.0-beta.8
• dependabot/go_modules/go-modules-updates-07f3a6036d
• dependabot/go_modules/go-modules-updates-3c0b262fbe
• dependabot/go_modules/go-modules-updates-3c24d51eea
• dependabot/go_modules/go-modules-updates-7c4956ecd3
• dependabot/go_modules/go-modules-updates-8c36577aaf
• dependabot/go_modules/go-modules-updates-db33c82b2d
• dependabot/go_modules/go-modules-updates-e93809617c
• feature/v1.1
• fix-default-root-user
• mixerr
• mod
• modernize-ci-and-deps
• paskal/dependabot-disable-updates
• paskal/dependabot-security-updates
• refs/tags/v1.4.1
• v1.1.0

Build # 22532539397

Build Type

push

github

Committed by web-flow

Commit Message

Run as root by default to fix docker socket access (#58)

* Run as root by default to fix docker socket access

Previously, the container ran as non-root user app (UID 1001) which
failed on most systems because the docker socket GID didn't match
the container's docker group GID (999). The v1.3.0 image ran as root
and worked out of the box; v1.4.0 switched to non-root via the
updated baseimage and broke existing setups.

Set APP_UID=0 in the Dockerfile to restore root execution as default.
Add documented APP_UID/DOCKER_GID options in docker-compose.yml and
a "Running as Non-Root" section in README for users who prefer to
drop privileges.

Resolves #57

* keep TIME_ZONE commented out in docker-compose.yml

---------

Co-authored-by: umputun <umputun@gmail.com>

Coverage Stats

384 of 484 relevant lines covered (79.34%)

7.48 hits per line