This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2208040 - Ensure /dev/random and /dev/urandom even if run in a container
Summary: Ensure /dev/random and /dev/urandom even if run in a container
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: dracut
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Pavel Valena
QA Contact: qe-baseos-daemons
URL:
Whiteboard: ostree
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-17 18:43 UTC by Colin Walters
Modified: 2023-09-20 23:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-20 23:25:34 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github dracutdevs dracut pull 2331 0 None Draft Always ensure /dev/{u,random} are in initramfs 2023-05-17 18:44:31 UTC
Red Hat Issue Tracker   RHEL-5718 0 None Migrated None 2023-09-20 23:25:26 UTC
Red Hat Issue Tracker RHELPLAN-157539 0 None None None 2023-05-17 18:46:15 UTC

Description Colin Walters 2023-05-17 18:43:07 UTC 
Particularly with FIPS mode, it's required to have /dev/random and /dev/urandom in the initramfs.  Today we usually run dracut in a fully privileged environment (e.g. a host system as root, or a build system for Image Builder/rpm-ostree).

However, with https://fedoraproject.org/wiki/Changes/OstreeNativeContainer we want to enable a use case that looks like

```
$ cat Dockerfile
FROM quay.io/fedora/fedora-coreos:stable
ADD /path/to/foo /usr/lib/dracut/modules.d
RUN dracut
```

to inject a dracut module and regenerate the initramfs.  

The default podman/docker policy denies creation of device nodes.  However, we don't actually need to create "real" devices - we just need them to end up in the initramfs file.

https://github.com/dracutdevs/dracut/pull/2331 is an upstream PR that aims to address this.  Can you take a look?

Basically we need to ensure that we always have the device nodes in the initramfs, regardless of FIPS mode or not.
Comment 1 Colin Walters 2023-06-14 18:01:08 UTC 
Can someone who maintains dracut please take a look at this issue and comment upstream or here?

This is part of enabling "CoreOS Layering" for OCP https://docs.openshift.com/container-platform/4.13/post_installation_configuration/coreos-layering.html as well as outside of it.
Comment 2 Pavel Valena 2023-06-29 14:30:10 UTC 
I've looked into the upsteram PR and apart from the stored {u,}random file it looks OK. I'll look into making this PR viable for upstream.
Comment 3 Joseph Marrero 2023-06-29 14:59:31 UTC 
Thank you so much Pavel! Let me know if there is anything you need from us.
Comment 5 Pavel Valena 2023-08-16 12:14:22 UTC 
Postponing, as there is some kernel activity expected first, to be able to implement required dracut changes (as in line with PR discussion). Please let me know if I've missed something actionable.

[1] https://github.com/dracutdevs/dracut/pull/2331#issuecomment-1662821979
Comment 6 RHEL Program Management 2023-09-20 23:24:41 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 7 RHEL Program Management 2023-09-20 23:25:34 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.