Bug ID 1012390
Summary systemd-nspawn does not work if a container is a symlink
Classification openSUSE
Product openSUSE Distribution
Version Leap 42.2
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Basesystem
Assignee systemd-maintainers@suse.de
Reporter ebischoff@suse.com
QA Contact ebischoff@suse.com
Found By ---
Blocker ---

(not same bug as bsc#968573 - systemd fails on symlink)

On openSUSE Leap 42.2 (systemd version 228), if one does

    # systemd-nspawn -D mycontainer

and if mycontainer is a symlink to a real container directory, the command
fails with message:

    Failed to open root file system:
    Too many levels of symbolic links

which is annoying, because it is practical to select a container through a
symbolic link.

This bug is already known upstream:

   https://github.com/systemd/systemd/issues/2001

and this bug report is mostly for tracking its resolution.


You are receiving this mail because: