[systemd-devel] Failed to start Container: minus sign is replaced to slash in container name

[Stefan Schweter]

Am 02.06.2016 um 01:27 schrieb Stefan Schweter:
> Hi Lennart and all other systemd users,
> 
> I tried to enable + start a container named debian-sid. E.g. the
> following command works without any problems:
> 
> systemd-nspawn -M debian-sid
> 
> Then I used the machinectl tool for enabling the container:
> 
> [root at build ~]# machinectl enable debian-sid
> Created symlink
> /etc/systemd/system/machines.target.wants/systemd-nspawn at debian\x2dsid.service
> → /usr/lib/systemd/system/systemd-nspawn at .service.
> 
> When starting the container:
> 
> [root at build ~]# machinectl start debian-sid
> Job for systemd-nspawn at debian\x2dsid.service failed because the control
> process exited with error code.
> See "systemctl status "systemd-nspawn at debian\\x2dsid.service"" and
> "journalctl -xe" for details.
> 
> The output of the journalctl is:
> 
> Jun 02 01:21:40 build.name.eu systemd-nspawn[6477]: Invalid machine
> name: debian\x2dsid
> Jun 02 01:21:40 build.name.eu systemd[1]:
> systemd-nspawn at debian\x2dsid.service: Main process exited, cod
> Jun 02 01:21:40 build.name.eu systemd[1]: Failed to start Container
> debian\x2dsid.
> -- Subject: Unit systemd-nspawn at debian\x2dsid.service has failed
> -- Defined-By: systemd
> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
> -- -- Unit systemd-nspawn at debian\x2dsid.service has failed.
> -- -- The result is failed. How can I start the container with
> machinectl? It worked with previous systemd versions :) Tested with
> systemd 230 on Arch Linux. Thanks again + regards, Stefan

Hi,

I did further testing on the case mentioned above:

machinectl enable debian-sid

and

systemctl start systemd-nspawn at debian-sid

starts the container (btw: that wasn't working in version 228). But when
using:

machinectl start debian-sid

the "Invalid machine" error message still appears. The systemd-escape
tool won't help in this case, as machinectl start `systemd-escape
debian-sid` leads to an "Invalid machine name debian\x2dsid." message.

Can someone confirm this behaviour?

Thanks again + regards,

Stefan