Arch Linux

Convergence

Member

Registered: 2005-07-02

Posts: 377

Systemd Container Troubles (systemd-nspawn)

I'm trying to set up a chroot-like environment where I can test some things out.  I first tried chroot, but that failed because I need to use systemd within this environment.  I googled, and found out that I needed to use systemd's own nspawn function to do this.  So, I followed the wiki here: https://wiki.archlinux.org/index.php/Ar … _container

That fails though.  The boot process never finishes.  A lot of the services fail, and it loops between failing to start the logging system, and failing to create a login session.  The wiki mentions using the install image to run the container, but that's really not what I want to do.  Here is a sample of the output:

Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
         Stopping Journal Service...
[  OK  ] Stopped Journal Service.
         Starting Journal Service...
[  OK  ] Started Journal Service.
[FAILED] Failed to start Login Service.
See 'systemctl status systemd-logind.service' for details.
         Stopping Login Service...
[  OK  ] Stopped Login Service.
         Startin

Any suggestions?  Is running from the install disc the only way to make this work?  That would kind of defeat my purpose.

Last edited by Convergence (2014-04-26 20:03:47)

---

It's a very deadly weapon to know what you're doing
---  William Murderface