You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ lxc launch ubuntu:24.04 test-vm --vm
Launching test-vm
$ lxc shell test-vm
root@test-vm:~# sudo systemd-creds encrypt --name mysecret - - <<< "This is my secret"
Credential secret file '/var/lib/systemd/credential.secret' is not located on encrypted media, using anyway.
Whxqht+dQJax1aZeCGLxmiAAAAABAAAADAAAABAAAAAcUj13M+IcC190+ogAAAAAfZyQGcWRki/NlD+
2rS/pMtU+jXI4IP44AU5qcwPikPALoHmiGXEaqhtzNsNop6DvrJrqiAkLbvZYbwOgJSIBESCd
root@test-vm:~# sudo snap install lxd
2025-04-15T17:11:34Z INFO Waiting for automatic snapd restart...
lxd (5.21/stable) 5.21.3-c5ae129 from Canonical✓ installed
root@test-vm:~# lxd init --auto
root@test-vm:~# lxc launch ubuntu:24.04 test-vm-container
Launching test-vm-container
root@test-vm:~# lxc shell test-vm-container
root@test-vm-container:~# sudo systemd-creds encrypt --name mysecret - - <<< "This is my secret"
Credential secret file '/var/lib/systemd/credential.secret' is not located on encrypted media, using anyway.
Failed to determine local credential host secret: No such file or directory
I've just tested with Ubuntu 24.10 (vm and container), which has systemd 256, and the issue seems to go away. Perhaps this is actually a bug in systemd that has since been fixed.
Please confirm
Distribution
Ubuntu
Distribution version
24.10
Output of "snap list --all lxd core20 core22 core24 snapd"
Output of "lxc info" or system info if it fails
Issue description
I seem to end up with a broken systemd configuration when I launch a container inside of a VM.
It works fine with a container on the host.
Steps to reproduce
From the host
Starting from the host again
strace of failing command
Information to attach
dmesg
)lxc info NAME --show-log
)lxc config show NAME --expanded
)/var/log/lxd/lxd.log
or/var/snap/lxd/common/lxd/logs/lxd.log
)--debug
--debug
(or uselxc monitor
while reproducing the issue)The text was updated successfully, but these errors were encountered: