[GH-ISSUE #575] Bastion users dont align with UID_MAX and GID_MAX #148

Closed
opened 2026-05-07 00:19:25 +02:00 by BreizhHardware · 1 comment

Originally created by @jon4hz on GitHub (Aug 27, 2025).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/575

Hi there,

When installing the bastion (v3.21.00) I noticed that the install script tries to create a few users, which don't align with the default UID_MAX and GID_MAX.

Both those options are set to 60000 by default, but the bastion creates a healthcheck user with the UID 99999.

As a result, some commands like chown don't work because they require a valid UID/GID.

chown: changing ownership of '/home/healthcheck/.ssh/id_healthcheck': Invalid argument
chown: changing ownership of '/home/healthcheck/.ssh/id_healthcheck.pub': Invalid argument

The same goes for the lastoshuser. That one gets the uid 10000 but SYS_UID_MAX usually is 999.

I'd expect that the bastion either adjust /etc/login.defs or at least a hint about this in the documentation.

Originally created by @jon4hz on GitHub (Aug 27, 2025). Original GitHub issue: https://github.com/ovh/the-bastion/issues/575 Hi there, When installing the bastion (v3.21.00) I noticed that the install script tries to create a few users, which don't align with the default UID_MAX and GID_MAX. Both those options are set to `60000` by default, but the bastion creates a `healthcheck` user with the UID `99999`. As a result, some commands like `chown` don't work because they require a valid UID/GID. ``` chown: changing ownership of '/home/healthcheck/.ssh/id_healthcheck': Invalid argument chown: changing ownership of '/home/healthcheck/.ssh/id_healthcheck.pub': Invalid argument ``` The same goes for the `lastoshuser`. That one gets the uid `10000` but `SYS_UID_MAX` usually is `999`. I'd expect that the bastion either adjust `/etc/login.defs` or at least a hint about this in the documentation.
Author
Owner

@jon4hz commented on GitHub (Aug 27, 2025):

okay nevermind, the actual issue is that I'm testing the installation in a podman container. So podman is the culprit...

<!-- gh-comment-id:3227507620 --> @jon4hz commented on GitHub (Aug 27, 2025): okay nevermind, the actual issue is that I'm testing the installation in a podman container. So podman is the culprit...
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/the-bastion#148
No description provided.