[systemd-devel] machinectl start vs. systemctl enable systemd-nspawn at ...

[Lennart Poettering]

On Mon, 22.06.15 10:36, Johannes Ernst (johannes.ernst at gmail.com) wrote:

> What’s the difference between
>     machinectl start foo
> and
>     systemctl start systemd-nspawn at foo
> ? They look the same to me. 

They are pretty much, as the man page even says.

It's a bit nicer to user "machinectl start foo" though, since if foo
contains weird chars, machinectl will apply the right escaping for
you, which is particularly useful when you container names contain
dashes.

Also, machinectl start has its own PolicyKit action, which means you
can grant that to specific users without having to grant them the
right to start any kind of service.

Lennart

-- 
Lennart Poettering, Red Hat