Bug#896687: systemd-container: EPERM when use syscall statx inside nspawn, with default filter

Zhang Jingqiang zh_jq at outlook.com
Mon Apr 23 16:47:09 BST 2018


Package: systemd-container
Version: 238-4
Severity: normal

Dear Maintainer,

I can use statx outside of the container, but always get EPERM in it.
I didn't set filters myself, just use the default ones.
The problem does not exsist with amd64 hosts.

Thanks

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: arm64 (aarch64)

Kernel: Linux 4.15.11-mainline-rev1 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd-container depends on:
ii  dbus             1.12.6-2
ii  libacl1          2.2.52-3+b1
ii  libbz2-1.0       1.0.6-8.1
ii  libc6            2.27-3
ii  libcurl3-gnutls  7.58.0-2
ii  libgcrypt20      1.8.2-2
ii  liblzma5         5.2.2-1.3
ii  libseccomp2      2.3.1-2.1
ii  libselinux1      2.7-2+b2
ii  systemd          238-4
ii  zlib1g           1:1.2.8.dfsg-5

Versions of packages systemd-container recommends:
ii  btrfs-progs        4.15.1-2
ii  libnss-mymachines  238-4

systemd-container suggests no packages.

-- no debconf information



More information about the Pkg-systemd-maintainers mailing list