Bug 88973 - systemd-nspawn: No proper error handling when pointing --bind to non-existent directory
Summary: systemd-nspawn: No proper error handling when pointing --bind to non-existent...
Status: RESOLVED FIXED
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-04 22:24 UTC by Elias Probst
Modified: 2017-11-20 16:39 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Elias Probst 2015-02-04 22:24:26 UTC
When pointing --bind to a non-existent directory, systemd-nspawn will fail with "Failed to register machine: Interrupted system call" but doesn't show any clear message why it failed.

systemd-nspawn should check the validity of a path in --bind before attempting to launch the instance.
If the path is invalid, it should show an error message like:
"Path /foo/bar is invalid"


The same goes for --bind-ro
Comment 1 Lennart Poettering 2017-11-20 16:39:49 UTC
Current versions will print the error message "Failed to stat /quux: No such file or directory", which I figure is good enough. Closing.


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.