RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

When using subscription-manager from inside a rhel container using podman as a non-root user (on the container host), subscription-manager is unable to detect it is running inside a container.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. podman run -it --rm registry.redhat.io/rhel7:latest /bin/bash
# Now inside the container
2. subscription-manager status
+-------------------------------------------+
   System Status Details
+-------------------------------------------+
Overall Status: Unknown

System Purpose Status: Unknown

# ^^ We should have been informed subman is not enabled in containers

Actual results:

Subman operates as if it is not running in a container


Expected results:
After running any subman command I expect we'll see:
"""
subscription-manager is disabled when running inside a container. Please refer to your host system for subscription management.
"""


Additional info:
If you start podman as root (in the first step above) subman behaves as expected in the container

I believe this is caused by podman not being able to fully populate /run/secrets/rhsm due to permissions on the host.

You could check if their is an environment variable CONTAINER 

$ podman run fedora printenv container
oci

We set that on all of the container engines.

There is also a /run/.containerenv
file

$ podman run fedora ls /run/.containerenv
/run/.containerenv

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.