systemd will generate a new machine-id if /etc/machine-id is empty,
that's how anaconda does it, maybe it's also an option for guestfish.
- fabian
On Tue, Mar 29, 2016 at 1:14 PM, Richard W.M. Jones <rjones(a)redhat.com> wrote:
Currently when the appliance is booted we see warning messages like
these ones:
[/usr/lib/tmpfiles.d/systemd.conf:26] Failed to replace specifiers: /run/log/journal/%m
[/usr/lib/tmpfiles.d/systemd.conf:28] Failed to replace specifiers: /run/log/journal/%m
[/usr/lib/tmpfiles.d/systemd.conf:29] Failed to replace specifiers: /run/log/journal/%m
They are apparently harmless, but are caused because /etc/machine-id
does not exist inside the appliance, and so %m cannot be substituted
by systemd-tmpfiles.
The solution to this is to provide /etc/machine-id. However this is
not so simple: either we could get supermin to generate this,
requiring an ugly systemd-specific hack to supermin, or we could
generate it in the /init script, which just slows the init script down
for no real reason.
Since the content of /etc/machine-id doesn't really matter for a
throwaway appliance so long as it has the right format, this commit
copies the host file into the appliance.
---
appliance/hostfiles.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/appliance/hostfiles.in b/appliance/hostfiles.in
index 8ff53b5..6c581bd 100644
--- a/appliance/hostfiles.in
+++ b/appliance/hostfiles.in
@@ -13,5 +13,6 @@ dnl SUSE=1 For OpenSUSE.
dnl FRUGALWARE=1 For Frugalware.
dnl MAGEIA=1 For Mageia.
+/etc/machine-id
/lib/lsb/*
/usr/share/augeas/lenses/*.aug
--
2.7.4
_______________________________________________
Libguestfs mailing list
Libguestfs(a)redhat.com
https://www.redhat.com/mailman/listinfo/libguestfs
--
Fabian Deutsch <fdeutsch(a)redhat.com>
RHEV Hypervisor
Red Hat