From: Anton Mikanovich <amikan@ilbers.de>
To: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>,
jan.kiszka@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH v3] classes/image-postproc-extension: Remove /etc/machine-id
Date: Sat, 14 May 2022 17:04:09 +0300 [thread overview]
Message-ID: <74051d61-fcab-0300-9d9b-4619b8e05acc@ilbers.de> (raw)
In-Reply-To: <20220420130044.668017-1-Quirin.Gylstorff@siemens.com>
20.04.2022 16:00, Quirin Gylstorff wrote:
> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
>
> In a read-only system the machine id should be deleted or
> set to `unitialized\n`[1].
>
> Systemd will generate a new machine-id during the first boot.
> In the case of a read-only root file system Systemd generates a mount point with
> the machine id. If an overlay for /etc is used this creates a mount conflict.
> To avoid the conflict between the overlay filesystem and systemd /etc/machine-id
> mount point deleted the file /etc/machine-id.
>
>
> This partly reverts 98d6a72d3064. The man page[2] was updated for Debian Bullseye to
> allow a missing machine id. For Debian Bullseye it reads:
>
> ```
> For operating system images which are created once and used on multiple machines,
> for example for containers or in the cloud, /etc/machine-id should be either missing
> or an empty file in the generic file system image
> ```
>
> [1]: https://systemd.io/BUILDING_IMAGES/
> [2]: https://manpages.debian.org/bullseye/systemd/machine-id.5.en.html
>
> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
Applied to next, thanks.
next prev parent reply other threads:[~2022-05-14 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 15:36 [PATCH] " Q. Gylstorff
2022-04-19 16:15 ` Jan Kiszka
2022-04-20 9:00 ` Henning Schild
2022-04-19 19:10 ` Anton Mikanovich
2022-04-20 7:28 ` [PATCH v2] " Quirin Gylstorff
2022-04-20 13:00 ` [PATCH v3] " Quirin Gylstorff
2022-05-14 14:04 ` Anton Mikanovich [this message]
2022-04-20 8:44 ` [PATCH] " Henning Schild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74051d61-fcab-0300-9d9b-4619b8e05acc@ilbers.de \
--to=amikan@ilbers.de \
--cc=Quirin.Gylstorff@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox