If you launch a container with IGNITION_GID=100, for example, there appears to be a conflict with a group definition within the image and the container exits.
Expected Behavior
Warning is logged, and ignition user within the container uses a primary GID that may overlap with an existing group definition (inside the container).
Actual Behavior
During remapping of ignition user UID/GID during entrypoint, a fatal error prevents container startup:
init | Launchers absent from image, enabling hosted launchers.
init | New Volume detected at /data, copying existing image files prior to Gateway Launch...
init | WARNING: Gateway is not initialized and no password option is specified
init | Disabling automated gateway commissioning, manual input will be required
init | Adjusting UID of 'ignition' user from 999 to 1026
init | Adjusting GID of 'ignition' user from 999 to 100
groupmod: GID '100' already exists
Description
If you launch a container with
IGNITION_GID=100, for example, there appears to be a conflict with a group definition within the image and the container exits.Expected Behavior
Warning is logged, and
ignitionuser within the container uses a primary GID that may overlap with an existing group definition (inside the container).Actual Behavior
During remapping of
ignitionuser UID/GID during entrypoint, a fatal error prevents container startup: