-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-8.8.0
-
None
-
Moderate
-
rhel-container-tools
-
3
-
False
-
False
-
-
None
-
Red Hat Enterprise Linux
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
1. Proposed title of this feature request
[RFE] recognize and apply /etc/subuid /etc/subgid modifications
3. What is the nature and description of the request?
For users starting podman the first time without any subuid / subgid mapping on a RHEL Workstation
a namespace is created and kept alive by the "podman pause" process. If the configuration of subuid /
subgid for the same user is modified, podman does not recognize until:
- Logout / Login -> The graphical working environment is gone and has to be re-opened.
- Kill podman pause process -> Killing a process feels not like intended.
- podman-system-migrate -> It's very likely this command is unknown to new users.
4. Why does the customer need this? (List the business requirements here)
- general improvement
5. How would the customer like to achieve this? (List the functional requirements here)
- Podman shall re-read /etc/subuid as appropriate so it can detect the user has been added in
the meantime (of course it can write a message about this to stdout).
6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
1) Execute a podman command without mapping configured -> check podman pause process is there
2) Adjust the subuid / subgid mappings for a logged in user
3) Try to start a rootless container as the logged in user
4) It works with the updated configuration in /etc/subuid and /etc/subgid
7. Is there already an existing RFE upstream or in Red Hat Bugzilla?
- not known
8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
- no asap
9. Is the sales team involved in this request and do they have any additional input?
- no
10. List any affected packages or components.
- podman-*
- probably kernel-*
11. Would the customer be able to assist in testing this functionality if implemented?
- yes