You are not logged in.

#1 2017-06-03 07:40:03

hexadecagram
Member
Registered: 2011-05-20
Posts: 27

[SOLVED] machinectl list no longer lists systemd-nspawn instances

Hello all,

In order to get my containers working in bridged mode, I have overridden each machine's systemd-nspawn@*.service unit with the following,

ExecStart=
ExecStart=/usr/bin/systemd-nspawn --quiet --keep-unit --boot --link-journal=try-guest --network-bridge=br0 -U --settings=override --machine=%I

the only difference being that I changed "--network-veth" to "--network-bridge=br0".

The command,

machinectl list

exits with status 1 and no output, whether I run it as a normal user or using sudo.

Any thoughts?

Last edited by hexadecagram (2017-09-05 07:39:00)

Offline

#2 2017-06-03 08:13:36

hexadecagram
Member
Registered: 2011-05-20
Posts: 27

Re: [SOLVED] machinectl list no longer lists systemd-nspawn instances

ADDITIONAL

If I run, e.g.,

machinectl status sumdumbox

I do get what one might expect on stdout and a 0 exit status.

Offline

#3 2017-09-05 07:33:44

hexadecagram
Member
Registered: 2011-05-20
Posts: 27

Re: [SOLVED] machinectl list no longer lists systemd-nspawn instances

This issue has been resolved, either since the inclusion of systemd-machined (unlikely; the announcement for systemd 205 was posted July 3, 2013), or because it wasn't enabled on my machine (or by default, it would seem).

Offline

Board footer

Powered by FluxBB