Bug 88973

Summary: systemd-nspawn: No proper error handling when pointing --bind to non-existent directory
Product: systemd Reporter: Elias Probst <mail>
Component: generalAssignee: systemd-bugs
Status: RESOLVED FIXED QA Contact: systemd-bugs
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

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.