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

Michael Biebl biebl at debian.org
Mon Apr 23 16:54:26 BST 2018


Control: tags -1 + moreinfo

Am 23.04.2018 um 17:47 schrieb Zhang Jingqiang:
> 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.

Please share more details about your setup:
- What commands you use to create the chroot
- What exact command line you use to start the nspawn container
- What command exactly you run inside the container

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20180423/222cdc46/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list