all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Oguz Bektas <o.bektas@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH container] fix #3443: setup: clear /etc/machine-id in post-create hook
Date: Wed, 26 May 2021 11:46:11 +0200	[thread overview]
Message-ID: <20210526094611.GC14375@gaia.proxmox.com> (raw)
In-Reply-To: <20210526094023.GB14375@gaia.proxmox.com>

On Wed, May 26, 2021 at 11:40:23AM +0200, Oguz Bektas wrote:
> hi,
> 
> thanks for checking
> 
> On Tue, May 25, 2021 at 03:45:53PM +0200, Thomas Lamprecht wrote:
> > On 25.05.21 15:17, Oguz Bektas wrote:
> > > this way when new containers are created the will have a unique
> > > /etc/machine-id
> > > 
> > 
> > why the dbus then? systemd talks explicitly only about /etc/machine-id
> > in the docs and also in their CT interface [0], the thematic is only touched
> > there though.
> > 
> > The dbus one is most often a symlink to /etc/machine-id, removing that can
> > break things...
> 
> 
> in our ubuntu templates it exists as a regular file (not symlinked).
> 
> so if that's not removed before first boot, it's copied to /etc/machine-id
> from there when the container boots.
> 
 

 also in the debian buster template. but not in the archlinux (there
 it's symlinked)




  reply	other threads:[~2021-05-26  9:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 13:17 Oguz Bektas
2021-05-25 13:45 ` Thomas Lamprecht
2021-05-26  9:40   ` Oguz Bektas
2021-05-26  9:46     ` Oguz Bektas [this message]
2021-05-26 10:00     ` Thomas Lamprecht
2021-05-26 10:03       ` Oguz Bektas
2021-05-26 10:07         ` Thomas Lamprecht

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=20210526094611.GC14375@gaia.proxmox.com \
    --to=o.bektas@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal