Package: systemd-container Version: 232-25+deb9u1 Severity: important Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I am running containers launched with systemd-nspawn. They show up in 'machinectl' just fine. * What exactly did you do (or not do) that was effective (or ineffective)? Running machinectl with the --no-legend flag causes it to report "No machines." *after* the actual list of machines. * What was the outcome of this action? admin@ip-172-31-15-145:~$ machinectl MACHINE CLASS SERVICE OS VERSION ADDRESSES ctr-emVnH3DhH3rStx3g78sGyh container systemd-nspawn alpine 3.6.2 10.1.16.204... 1 machines listed. admin@ip-172-31-15-145:~$ machinectl --no-legend ctr-emVnH3DhH3rStx3g78sGyh container systemd-nspawn alpine 3.6.2 10.1.16.204... No machines. * What outcome did you expect instead? That "No machines." would not be orinted. *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-container depends on: ii dbus 1.10.22-0+deb9u1 ii libacl1 2.2.52-3+b1 ii libblkid1 2.29.2-1 ii libbz2-1.0 1.0.6-8.1 ii libc6 2.24-11+deb9u1 ii libcurl3-gnutls 7.52.1-5+deb9u2 ii libgcrypt20 1.7.6-2+deb9u2 ii libip4tc0 1.6.0+snapshot20161117-6 ii liblzma5 5.2.2-1.2+b1 ii libseccomp2 2.3.1-2.1 ii libselinux1 2.6-3+b3 ii systemd 232-25+deb9u1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages systemd-container recommends: ii btrfs-progs 4.7.3-1 ii libnss-mymachines 232-25+deb9u1 systemd-container suggests no packages. -- no debconf information