Bug 46423 - systemd-nspawn: cryptic error when fails due to lack of adaquate namespace support
Summary: systemd-nspawn: cryptic error when fails due to lack of adaquate namespace su...
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: Lennart Poettering
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-21 18:32 UTC by Shawn Landden
Modified: 2012-03-12 12:31 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
hint the user of why clone() might fail (606 bytes, patch)
2012-02-21 18:32 UTC, Shawn Landden 		Details | Splinter Review
View All

Description Shawn Landden 2012-02-21 18:32:56 UTC 
Created attachment 57429 [details] [review]
hint the user of why clone() might fail

When running systemd-nspawn I got this cryptic error:

clone() failed: Invalid argument

Someone trying to help in #systemd was clueless as well, even when given the above error message.

I had to use strace, and then examine both the <linux/sched.d> and the systemd source in order to figure out this was due to me not compiling in comprehensive namespace support into my kernel.

Here is a patch that gives a more helpful error message for others that may compile their own kernel, or for other reasons end up with a kernel that can't run systemd-nspawn due to lack of CONFIG_*_NS features.

-Shawn

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.