mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-10 00:09:09 +02:00
[GH-ISSUE #575] Bastion users dont align with UID_MAX and GID_MAX #148
Labels
No labels
answered
bug
documentation
enhancement
enhancement
feature
feature
kept-open-for-info
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/the-bastion#148
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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
60000by default, but the bastion creates ahealthcheckuser with the UID99999.As a result, some commands like
chowndon't work because they require a valid UID/GID.The same goes for the
lastoshuser. That one gets the uid10000butSYS_UID_MAXusually is999.I'd expect that the bastion either adjust
/etc/login.defsor at least a hint about this in the documentation.@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...