arch-nspawn/systemd-nspawn issues under v218

justin-8 · 2014-12-29 06:40:27

So, I'm not completely sure this is the right sub-forum for this, but it sounded most fitting.

Since upgrading to systemd-218 (from 217) whenever arch-nspawn or even systemd-nspawn directly is called from a build script in jenkins, it has a return code of 1. I can't see why and it has no other output at all. Running the same commands from the build log as the jenkins user works exactly as intended and as it has for the past many systemd versions.

After eventually figuring out the problem was actually systemd-nspawn and not some logical-seeming change between versions, I've downgraded systemd to v217 and now it all works again swimmingly.

The script is here if anyone is interested, but it's pretty straightforward; just puts some locking around running multiple build agents on a single machine concurrently: https://github.com/justin8/puppet/blob/ … kg-jenkins

Does anyone have any ideas on what might cause this? or a way to show more debug info from systemd-nspawn?

bsaner · 2014-12-30 08:33:33

don't have time to check your script atm, but i'd recommend the following:

-sometimes systemd-nspawn chokes on pipes in the command if you're passing it directly (i.e. no -b). but only SOMETIMES.
-have you tried binding the journal for the nspawn'd machine? check out the --link-journal= option in the man page for systemd-nspawn; you may get some useful output there.

justin-8 · 2015-01-01 07:52:57

Thanks for that; the journal linking seems really useful; but when I attempt to run it:

$> systemd-nspawn --link-journal=host -D /chroot/root --register=no --bind=/var/cache/pacman/pkg/ pacman -Syu --noconfirm
Spawning container root on /chroot/root.
Press ^] three times within 1s to kill container.
Container root failed with error code 1.

Last edited by justin-8 (2015-01-01 07:53:12)

w-flo · 2015-03-04 23:37:12

Any solutions for this?

I have a jenkins script that executes extra-x86_64-build, which calls arch-nspawn. This fails in jenkins and prints no error message (but used to work a few months ago).

justin-8 · 2015-03-04 23:40:14

Stay on 217 at the moment. I was following the upstream bug and contributing some logs, it's supposed to be fixed in git for v219, so just stick to 217 until 219 is out.

w-flo · 2015-03-04 23:42:54

Okay, thanks for the quick reply. :-)

I guess I can manually run this rarely needed build until 219 is out.

justin-8 · 2015-03-05 00:27:19

No problem. I just got back to my computer now; here's the link to the bug if you were interested.

https://bugs.freedesktop.org/show_bug.cgi?id=87732

w-flo · 2015-03-05 11:48:44

Ah, that explains why the nspawn command issued by arch-nspawn works when manually pasting it into a terminal, but fails when jenkins does its magic. I'm glad this is already fixed upstream (by Lennart himself ), so it's only a matter of time until the job is back to normal operation.

Thanks again.

myles · 2015-03-07 21:40:37

If this is solved please edit the first post to add "[SOLVED]" to the title.

Arch Linux

#1 2014-12-29 06:40:27

arch-nspawn/systemd-nspawn issues under v218

#2 2014-12-30 08:33:33

Re: arch-nspawn/systemd-nspawn issues under v218

#3 2015-01-01 07:52:57

Re: arch-nspawn/systemd-nspawn issues under v218

#4 2015-03-04 23:37:12

Re: arch-nspawn/systemd-nspawn issues under v218

#5 2015-03-04 23:40:14

Re: arch-nspawn/systemd-nspawn issues under v218

#6 2015-03-04 23:42:54

Re: arch-nspawn/systemd-nspawn issues under v218

#7 2015-03-05 00:27:19

Re: arch-nspawn/systemd-nspawn issues under v218

#8 2015-03-05 11:48:44

Re: arch-nspawn/systemd-nspawn issues under v218

#9 2015-03-07 21:40:37

Re: arch-nspawn/systemd-nspawn issues under v218

Board footer