Bug#805785: systemd-container: machinectl start #containername# fails when /var/lib/machines/#containername# is symlink to other folder

[Denys]

Package: systemd-container
Version: 228-2
Severity: important

Dear Maintainer,

machinectl start #containername# fails when /var/lib/machines/#containername#
is symbolic link to other folder

systemd[1]: Starting Container jee...
systemd-nspawn[2798]: Failed to open root file system: Too many levels of
symbolic links
systemd[1]: systemd-nspawn at jee.service: Main process exited, code=exited,
status=1/FAILURE
systemd[1]: Failed to start Container jee.
systemd[1]: systemd-nspawn at jee.service: Unit entered failed state.
systemd[1]: systemd-nspawn at jee.service: Failed with result 'exit-code'.

ls -la /var/lib/machines
drwx------  2 root root 4096 Ноя 22 14:55 .
drwxr-xr-x 77 root root 4096 Ноя 22 14:06 ..
lrwxrwxrwx  1 root root   26 Ноя 22 14:24 jee ->
/home/#my_home_folder#/containers/jee

It have becomes after i install linux-image-4.3.0-trunk-amd64






-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=ru_UA.UTF-8, LC_CTYPE=ru_UA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-container depends on:
ii  libblkid1        2.27.1-1
ii  libbz2-1.0       1.0.6-8
ii  libc6            2.19-22
ii  libcap2          1:2.24-12
ii  libcurl3-gnutls  7.45.0-1+b1
ii  libgcrypt20      1.6.4-3
ii  liblzma5         5.1.1alpha+20120614-2.1
ii  libseccomp2      2.2.3-2
ii  libselinux1      2.4-3
ii  systemd          228-2
ii  zlib1g           1:1.2.8.dfsg-2+b1

systemd-container recommends no packages.

systemd-container suggests no packages.

-- no debconf information