pve-container update 7.2

[apmuthu]

Today's update:

# apt-get update
Hit:1 http://security.debian.org bullseye-security InRelease
Hit:2 http://ftp.debian.org/debian bullseye InRelease
Hit:3 http://ftp.debian.org/debian bullseye-updates InRelease
Hit:4 http://download.proxmox.com/debian/pve bullseye InRelease
Reading package lists... Done
root@pr72:~# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  libc-bin libc-l10n libc6 locales pve-container
5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 8,738 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y

The systemd is to now respect the parameter but defaults to "No"

# needed because instances of template service units automatically
# get their own slice with DefaultDependencies=yes, regardless of
# the DefaultDependencies value of the template unit
#
# see man systemd.service and pve-container@.service
[Unit]
Description=PVE LXC Container Slice
DefaultDependencies=No
Documentation=man:pct

Locating the contained file in the host has a backward slash in the file path:

# locate x2dcontainer.slice
/usr/lib/systemd/system/system-pve\x2dcontainer.slice

The listing in the host reveals:

# ls -al /usr/lib/systemd/system
....
-rw-r--r--  1 root root   329 Oct 21 18:26 'system-pve\x2dcontainer.slice'
-rw-r--r--  1 root root   442 Feb  2  2021 'system-systemd\x2dcryptsetup.slice'
....

Is this the intended backslash file naming at the last folder ?

The change log in pve-container_4.2-3_all.deb shows:

pve-container (4.2-3) bullseye; urgency=medium

  * fix #4164: use DHCP=yes instead of DHCP=both in systemd-networkd config

  * apply pending mountpoint: also hotplug non-volume mount points

  * support Ubuntu 22.10 Kinetic Kudu

 -- Proxmox Support Team <support@proxmox.com>  Fri, 21 Oct 2022 14:56:59 +0200

The /usr/share/perl5/PVE/LXC/Setup/Base.pm file now has line 264 changed to "yes" from "both" for dhcp as:

    my @DHCPMODES = ('no', 'v4', 'v6', 'yes');

 

[dcsapak]

Is this the intended backslash file naming at the last folder ?

do you mean the \x2d ? this is hex escaping for '-', see https://www.freedesktop.org/software/systemd/man/systemd-escape.html

do you have another question that i don't see here?

 

[apmuthu]

Wonder why a normal hyphen was not used instead of '\x2d' and why does it display so (decrypted) in the ls -al /usr/lib/systemd/system | grep system- | grep slice command ?

Will there be any problem if the escape string is replaced with a normal hyphen and can it be called consistently either way?

This appears to be the only set of instances in the PVE filesystem:

# locate \x2d
/usr/lib/systemd/system/system-pve\x2dcontainer.slice
/usr/lib/systemd/system/system-systemd\x2dcryptsetup.slice

 

[fiona]

Wonder why a normal hyphen was not used instead of '\x2d' and why does it display so (decrypted) in the ls -al /usr/lib/systemd/system | grep system- | grep slice command ?

It's to have a well-defined format for such file names, while still allowing arbitrary strings. See the STRING ESCAPING FOR INCLUSION IN UNIT NAMES section of man systemd.unit.

Will there be any problem if the escape string is replaced with a normal hyphen and can it be called consistently either way?

Of course there will be problems if you simply change such file names

 

[apmuthu]

@fiona - thanks for the explanation and potential renaming issues.

The said man page states that it is optional to do so and such escaping is in vogue in PVE since v3.4.

 systemd-escape
    may be used to escape strings for inclusion in systemd unit names. The command may be used to escape and to undo escaping of strings.

Wonder why specifically the said 2 .slice filenames were so constructed when such escaping was optional.