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:

Attempt to run systemd-tmpfiles --create in containers started under docker-1.1.2-9.el7.x86_64 complains about

[/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /var/log/journal/%m
[/usr/lib/tmpfiles.d/systemd.conf:28] Failed to replace specifiers: /run/log/journal/%m

Looking around documentation and code, the %m is supposed to get the id from /etc/machine-id, and that is supposed to be 32 bytes + newline, and systemd-tmpfiles checks that it is not longer.

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

docker-1.1.2-9.el7.x86_64

How reproducible:

Deterministic.

Steps to Reproduce:
1. # docker run -ti rhel7 wc /etc/machine-id
2. # docker run -ti fedora:20 wc /etc/machine-id

Actual results:

 1  1 65 /etc/machine-id

Expected results:

 1  1 33 /etc/machine-id

Additional info:

systemd guys, is there any reason for this hard limit.  We want to set the /etc/machine-id to match the UUID of the docker container.  Docker sets it UUID to 64

systemd refuse to fix this, claim that this is a docker problem.  UUID should be 32 chars.

I don't see either side fixing this,

Can't DOcker just put part of its UUID there?

The current patch working its way upstream is to set the container_uuid environment variable with the truncated UUID before starting systemd within the container.  According to documentation systemd is supposed to create /etc/machine-id if it does not exist and this environment variable is set.  I believe we have another bug report where systemd did not do this, but not sure what the problem is.


If you play with docker-1.2 in collider right now the container_uuid environment variable should be set.