From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <o.bektas@proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 0574172C72 for <pve-devel@lists.proxmox.com>; Wed, 26 May 2021 11:46:14 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id EECB010090 for <pve-devel@lists.proxmox.com>; Wed, 26 May 2021 11:46:13 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 87A2A10084 for <pve-devel@lists.proxmox.com>; Wed, 26 May 2021 11:46:13 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 55214465B1 for <pve-devel@lists.proxmox.com>; Wed, 26 May 2021 11:46:13 +0200 (CEST) Date: Wed, 26 May 2021 11:46:11 +0200 From: Oguz Bektas <o.bektas@proxmox.com> To: Thomas Lamprecht <t.lamprecht@proxmox.com>, Proxmox VE development discussion <pve-devel@lists.proxmox.com> Message-ID: <20210526094611.GC14375@gaia.proxmox.com> Mail-Followup-To: Oguz Bektas <o.bektas@proxmox.com>, Thomas Lamprecht <t.lamprecht@proxmox.com>, Proxmox VE development discussion <pve-devel@lists.proxmox.com> References: <20210525131711.1007675-1-o.bektas@proxmox.com> <bc3cd68f-8780-04ce-2fa3-8b6bef19f787@proxmox.com> <20210526094023.GB14375@gaia.proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210526094023.GB14375@gaia.proxmox.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-SPAM-LEVEL: Spam detection results: 1 AWL 1.143 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH container] fix #3443: setup: clear /etc/machine-id in post-create hook X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Wed, 26 May 2021 09:46:14 -0000 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)