Package: linux-image-grsec-amd64
Version: 10
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
I can not start lxc unprivileged container with
linux-image-grsec-amd64 kernel (even start as root),
The setup work very well with normal debian kernel (start as root or
nonroot),
I googled "grsec + newuidmap",
look like the problem is grsec break /proc readable by other user.
(Please correct me, if I am wrong).
I want to know, is it possible start lxc unprivileged container with
grsec kernel? (start as root or nonroot)
Thanks.
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.7.0-1-grsec-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages linux-image-grsec-amd64 depends on:
ii linux-image-4.7.0-1-grsec-amd64 4.7.5-1+grsec201609261522+1
linux-image-grsec-amd64 recommends no packages.
linux-image-grsec-amd64 suggests no packages.
-- no debconf information
