systemd services fails on freshly launched debian/12 image.

[WaltWilliams]

• Distribution: Debian
• Distribution version: 12
• The output of systemctl --type=service

  UNIT                               LOAD   ACTIVE SUB     DESCRIPTION                                      
  console-getty.service              loaded active running Console Getty
  dbus.service                       loaded active running D-Bus System Message Bus
● e2scrub_reap.service               loaded failed failed  Remove Stale Online ext4 Metadata Check Snapshots
● systemd-hostnamed.service          loaded failed failed  Hostname Service
  systemd-journal-flush.service      loaded active exited  Flush Journal to Persistent Storage
  systemd-journald.service           loaded active running Journal Service
  systemd-logind.service             loaded active running User Login Management
  systemd-networkd.service           loaded active running Network Configuration
  systemd-remount-fs.service         loaded active exited  Remount Root and Kernel File Systems
  systemd-resolved.service           loaded active running Network Name Resolution
  systemd-sysctl.service             loaded active exited  Apply Kernel Variables
  systemd-sysusers.service           loaded active exited  Create System Users
  systemd-tmpfiles-setup-dev.service loaded active exited  Create Static Device Nodes in /dev
  systemd-tmpfiles-setup.service     loaded active exited  Create Volatile Files and Directories
  systemd-udev-trigger.service       loaded active exited  Coldplug All udev Devices
  systemd-udevd.service              loaded active running Rule-based Manager for Device Events and Files
  systemd-update-utmp.service        loaded active exited  Record System Boot/Shutdown in UTMP
  systemd-user-sessions.service      loaded active exited  Permit User Sessions
  user-runtime-dir@0.service         loaded active exited  User Runtime Directory /run/user/0
  user@0.service                     loaded active running User Manager for UID 0

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
23 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

dmesg fails as well.

root@Debian12:/var/www/sss# dmesg
dmesg: read kernel buffer failed: Operation not permitted

A brief description of what failed or what could be improved.

systemd-hostnamed.service and e2scrub_reap.service fails on start up.

The debian/12/cloud image has the same issue.

Steps to reproduce

Freshly launched image.

Information

On a different debian/12 image I was trying to determine why I'm unable to connect (ssh) to MariaDB from the host machine in IntelliJ DataGrip database management application when I found this. Judging by what I have read about what systemd-hostnamed.service does, I'm betting the hostnamed service failing is the cause of my failure in Datagrip.

Some postings I have read suspect AppArmor is the cause of the systemd failures.

[gibmat]

systemd-hostnamed.service is likely failing because it has PrivateNetwork=yes in its definition. Unfortunately the root cause is a known bug in the 6.1 kernel involving an apparmor bug that was fixed in 6.2 but hasn't yet been backported to the 6.1 tree. There's more discussion in Debian bugs 1052934 and 1050256; workarounds include modifying the service definitions, installing a kernel from bookworm-backports on the host, or disabling apparmor protections for the container.