I have tried all of the 'polite' exit signals within expect and the issue persists.
--console=interactive is already set by default and thus makes no difference. I wrote a short test script in expect to prove to myself I had exited the container - It launches via a spawned process the container, echoes the hostname then exits the container & back to the expect shell where the last two exiting messages are being written by expect 'puts' - eharman@ubuntu-2604:~$ ./test.sh spawn sudo systemd-nspawn -D /var/lib/machines/noble -u rms [sudo: authenticate] Password: ░ Spawning container noble on /var/lib/machines/noble. ░ Press Ctrl-] three times within 1s to kill container; two times followed by r ░ to reboot container; two times followed by p to poweroff container. ^[]11;rgb:0000/0000/0000^[\rms@noble:~$ cat /etc/hostname noble rms@noble:~$ rms@noble:~$ echo -ne '/x1D/x1D/x1D' /x1D/x1D/x1Drms@noble:~$ Exited spawned process Now exiting expect.. eharman@ubuntu-2604:~$ 11;rgb:0000/0000/0000 ..the trailing 11;rgb:0000/0000/0000 is an artefact of some regression bug in ANSI code handling maybe Xterm - - whilst messy I can live with it... If I run the script on the connected phys console it runs clean with no ANSI garbage... Output of df post script - Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 708508 1412 707096 1% /run /dev/mapper/ubuntu--vg-ubuntu--lv 59643812 11819788 44761856 21% / tmpfs 1771260 0 1771260 0% /dev/shm efivarfs 128 79 45 64% /sys/firmware/efi/efivars none 1024 0 1024 0% /run/credentials/systemd-journald.service tmpfs 1771264 0 1771264 0% /tmp none 1024 0 1024 0% /run/credentials/systemd-resolved.service /dev/sda2 1992552 190156 1681156 11% /boot /dev/sda1 1098628 6452 1092176 1% /boot/efi tmpfs 354252 8 354244 1% /run/user/1000 none 1024 0 1024 0% /run/credentials/systemd-networkd.service none 1024 0 1024 0% /run/credentials/[email protected] tmpfs 4096 0 4096 0% /run/systemd/nspawn/unix-export/noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2154625 Title: container has left an orphaned mount point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2154625/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
