-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Description
Steps To Reproduce
bitwarden-web as part of the docker installation fails to start again after updating to 2025.8.2.
I do regular bitwarden updates via the bitwarden.sh script, the updated failes to run since my most recent update at 00:00 AM on September 7th which installed bitwarden-web version 2025.8.2.
No changes in config or system since months, bitwarden-web previous to 2025.8.0 worked, 2025.8.0 failed, 2025.8.1 worked again, 2025.8.2 fails again.
Expected Result
Container shall start and run without error.
Actual Result
error: failed switching to "bitwarden:bitwarden": unable to find user bitwarden: no matching entries in passwd file
chown: unknown user/group bitwarden:bitwarden
chown: unknown user/group bitwarden:bitwarden
chown: unknown user/group bitwarden:bitwarden
chown: unknown user/group bitwarden:bitwarden
Screenshots or Videos
No response
Additional Context
The story looks exactly like the recently fixed 2025.8.0 bug to me which was reported here #6233 and solved by 2025.8.1.
2025.8.2 fails exactly like 2025.8.0 did. No change in system or settings:
2025.8.0 failed -> 2025.8.1 worked -> 2025.8.2 fails again.
Build Version
2025.8.2
Environment
Self-Hosted
Environment Details
Synology DS1819+ running DSM 7.2.2-72806 Update 4 (Linux) and bitwarden.sh
My bitwarden UID and GID indeed are 65534, the bitwarden.sh once added user and group with that high IDs:
admin@DiskStation2:/volume1/docker/bwdata/env$ more uid.env LOCAL_UID=65534 LOCAL_GID=65534 admin@DiskStation2:/volume1/docker/bwdata/env$ id -u bitwarden 65534 admin@DiskStation2:/volume1/docker/bwdata/env$ id -g bitwarden 65534 admin@DiskStation2:/volume1/docker/bwdata/env$
Issue Tracking Info
- I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.