Skip to main content
User guide

Subordinate IDs

Central subuid / subgid allocation for rootless containers; ranges are a fixed 65536, not selectable, never reclaimed; the statistics page shows what is left.

Rootless containers (podman, rootless docker) need each user to own a subordinate ID range in /etc/subuid and /etc/subgid. Maintaining those files per host leads to collisions; IPA allocates the ranges centrally and sssd 2.5+ serves them through its subid provider, so nothing is written on the host.

Subordinate IDs

Allocation rules

ItemValue
Range size per user65536, fixed
Startsequential from LINUX.IPA.TEST_subid_range (2147483648 upwards)
Per userat most one range; subuid and subgid start at the same value
Reclaimnever. After the user is deleted the range is dead, not reissued

Add allocates a range for the chosen user; users can also request their own (role Subordinate ID Selfservice User, empty by default). CLI: ipa subid-generate --owner=<user>.

Statistics

Subordinate ID statistics

ColumnMeaning
Base IDstart of the subordinate range
Assigned subordinate IDsranges handed out
Remaining subordinate IDsranges still available
Range sizetotal IDs the subordinate range holds
DNA remainingranges this server's DNA plugin still holds unissued (each master takes a slice)

The default range is 2147352576 IDs, enough for 32767 users.

Client

# /etc/nsswitch.conf
subid: sss

Supported from sssd 2.5; podman unshare cat /proc/self/uid_map showing the mapping means it works. Older clients keep hand-written /etc/subuid.

Boundaries

  • Range values cannot be chosen; a specific value means bypassing IPA and writing the file locally.
  • AD users cannot obtain subordinate IDs from IPA.

On this page