Service account renamed + directory permissions tightened, breaking non-root deployments

araiki

New Member
Context

We run WCS in a custom Docker image built on top of yours (FROM docker.io/flashphoner/webcallserver:<tag>), following the documented non-root pattern: our Dockerfile ends with USER flashphoner so the container never runs as root. This has worked unchanged since WCS 5.2.x. We just upgraded our base image from 5.3.414 to 5.3.492 and hit three breaking changes, none of which are mentioned in the release notes for that range.

1. The flashphoner service account was renamed

In 5.3.414, /etc/passwd has:
flashphoner:x:999:995::/home/flashphoner:/bin/sh

In 5.3.492, the same UID/GID now resolves to:
wcs-mcp-ctl:x:999:995:wcs-mcp-ctl service account:/nonexistent:/usr/sbin/nologin

Same UID/GID, different name. Any derived image with USER flashphoner (ours, and presumably anyone following the same documented pattern) now fails outright at docker run with:
docker: Error response from daemon: unable to find user flashphoner: no matching entries in passwd file

This isn't something a Dockerfile change on our side can fix gracefully without knowing the rename happened; we only found it by diffing /etc/passwd between the two image versions.

2. bin/webcallserver itself still hardcodes the old name

After switching our USER directive to the numeric 999:995 to work around point 1, we hit a second failure. bin/webcallserver has:
FLASHPHONER_USER="flashphoner"

and later compares it against getCurrentUser() (a reverse uid→name lookup) to decide whether it needs sudo -u flashphoner ... to start the java process, versus running it directly in-place when already running as that user. Since the reverse lookup now resolves to wcs-mcp-ctl, the comparison fails, the script falls back to sudo -u flashphoner, and that fails too since no sudoers rule grants it:
Code:
wcs-mcp-ctl is not in the sudoers file.
ERROR: FlashphonerWebCallServer cannot be started from user flashphoner, please fix the permissions to the folders or run 'webcallserver set-permissions'!

This breaks your own documented default: webcallserver --help still states it starts as flashphoner by default, but the script's own identity check no longer matches that default after the rename.

3. Install directory ownership/permissions were tightened

Independently of the rename, the entire WCS home directory changed ownership/mode:
  • 5.3.414: root:flashphoner, mode 775 (group-writable)
  • 5.3.492: root:root, mode 755 (not writable by the service account's group anymore)
This breaks non-root operation across the board: we saw Permission denied writing to conf/ (overwriting config files), creating logs/, writing the pid file under bin/, and symlinking records/ under client/. The error message points to webcallserver set-permissions as the fix, but nothing indicates this now needs to be run as part of a normal upgrade, or that it needs to run as root before the process drops privileges.

Our workaround (for context, not asking you to replicate it)

We re-added a flashphoner:x:999:995:... alias as the first entry in /etc/passwd//etc/group (so the reverse lookup resolves to flashphoner again) and did a recursive chown of the WCS home directory back to 999:995 in our own Dockerfile. This gets us running again, but it's clearly patching around your internal changes rather than a real fix.

Questions
  1. Is the account rename (flashphoner → wcs-mcp-ctl) and the ownership/permission tightening intentional and permanent, or could it be reconsidered?
  2. Is there a supported way to keep running non-root (as webcallserver --help still documents as the default) across this change, beyond manually re-adding the old account name and re-chowning everything ourselves?
  3. Could FLASHPHONER_USER in bin/webcallserver be derived dynamically (e.g. from getCurrentUser() itself, or from a config value) instead of being hardcoded, so a future account rename doesn't silently break the sudo/no-sudo branching again?
  4. Could this be called out in the release notes for anyone upgrading across this range?
 
Good day.
We do not rename the user account. Seems like user addition inside the container is broken. We raised the ticket WCS-5144 to investigate, will let you know about results.
 
Top