No hostname file created for rockylinux instance

Hello
I noticed that rocky linux containers (8, 8/cloud, 9, 9/cloud) created with incus 0.6 on my debian 12 host don’t come with /etc/hostname file.
On my other incus hosts (arch linux / incus 0.6 and fedora 39 / incus 0.5.1), the file is correctly created.
Incus config is the same on all my hosts.
Does anyone have the same issue?

Here is the cloudinit ouput

$ cloud-init status -l
status: error
boot_status_code: enabled-by-generator
last_update: Thu, 29 Feb 2024 18:03:28 +0000
detail:
('set_hostname', SetHostnameError("Failed to set the hostname to qp (qp): Unexpected error while running command.\nCommand: ['hostnamectl', 'set-hostname', 'qp']\nExit code: 1\nReason: -\nStdout: \nStderr: Could not set pretty hostname: Could not activate remote peer."))

Regards

It’s weird. There is supposed to be a /etc/hostname file.

After more research, I found out that systemd-hostnamed.service is crashing

× systemd-hostnamed.service - Hostname Service
     Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service; static)
    Drop-In: /usr/lib/systemd/system/systemd-hostnamed.service.d
             └─disable-privatedevices.conf
             /run/systemd/system/service.d
             └─zzz-lxc-service.conf
     Active: failed (Result: exit-code) since Fri 2024-03-01 09:33:20 UTC; 9s ago
       Docs: man:systemd-hostnamed.service(8)
             man:hostname(5)
             man:machine-info(5)
             man:org.freedesktop.resolve1(5)
    Process: 869 ExecStart=/usr/lib/systemd/systemd-hostnamed (code=exited, status=225/NETWORK)
   Main PID: 869 (code=exited, status=225/NETWORK)
        CPU: 857us

Mar 01 09:33:20 testtestq systemd[869]: systemd-hostnamed.service: Failed to set up network namespacing: Permission denied
Mar 01 09:33:20 testtestq systemd[869]: systemd-hostnamed.service: Failed at step NETWORK spawning /usr/lib/systemd/systemd-hostnamed: Permission denied
Mar 01 09:33:20 testtestq systemd[1]: Starting Hostname Service...
Mar 01 09:33:20 testtestq systemd[1]: systemd-hostnamed.service: Main process exited, code=exited, status=225/NETWORK
Mar 01 09:33:20 testtestq systemd[1]: systemd-hostnamed.service: Failed with result 'exit-code'.
Mar 01 09:33:20 testtestq systemd[1]: Failed to start Hostname Service.

As described in this issue Services configured with `PrivateNetwork=yes` fail to start in containers · Issue #29526 · systemd/systemd · GitHub, the unit works fine when using PrivateNetwork=no instead of PrivateNetwork=yes in systemd-hostnamed.service, and the command hostnamectl set-hostname xxx execute successfully after that.