Repository navigation
Release v3.7.8 - Optional PUID/PGID ownership remap for Unraid/home servers
✨ New Features
- Added optional
PUID/PGIDsupport for container file ownership mapping. On startup, the entrypoint now acceptsPUID/PGID(default999:999) and remaps the internalconverteraccount before launching the app. This aligns output ownership with host conventions used by Unraid and other home-server setups. - Safe GID fallback for common Unraid defaults. When
PGIDpoints to a GID that already exists in the base image (for example100), the startup remap falls back fromgroupmodtousermod -gsoconverteris reassigned to the existing group instead of failing. - Privilege drop now handled by
gosuin entrypoint. The image installsgosu, keeps startup as root only long enough to perform optional remapping, then immediately re-execs asconverter.
🔧 Internal
Dockerfilenow installsgosuand no longer setsUSER converterat build time.entrypoint.shnow:- validates
PUID/PGIDare numeric, - remaps converter UID/GID when needed,
- preserves old behavior when env vars are unset (
999:999), - drops privileges with
exec gosu converter "$0" "$@".
- validates
📚 Documentation
- Updated
README.md,DOCKER-COMPOSE.md,DEPLOYMENT.md, and compose examples to documentPUID/PGIDas an optional runtime ownership setting.
⚠️ Upgrade Notes
- No action required. With
PUID/PGIDunset the container behaves exactly as before (converter:converterat999:999). - To get host-correct ownership on Unraid: set
PUID=99andPGID=100. On other home-server setups, set them to the UID/GID of the user that owns the host directory you bind-mount. - If you already pin
--userondocker run/compose, the container starts non-root and the remap is skipped. A warning is emitted in that case so the no-op is visible.
Closes #64. Thanks @humaintenance for the well-scoped feature request and the working entrypoint snippet.