Can you please try the patch that has been attached to the bug and tell
me if it's fixing your issue?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823184#44
Le 13/05/16 à 17:49, Laurent Bigonville a écrit :
Le 13/05/16 à 17:16, Yuri D'Elia a écrit :
On Fri, May 13 2016, Laurent Bigonville<bi...@debian.org> wrote:
Again this is supposed to happen at early boot, and at this stage, only
PID1 exists. So I doubt there is a lot of concurrent processes at that time.
But this is not checked in the source.
In fact, this behavior will happen irregardless of the boot stage.
It doesn't do anything if /proc is already mounted, which is IMHO
expected on a fully booted machine and even container.
Even if the fix is simply the removal of the mountpoint, I consider the
solution broken by design.
What about mounting /proc really early?
I can say the same about initramfs. Can't initramfs just mount /proc
sooner and fix the problem correctly?
initramfs in debian is, like I said, already doing so.
SELinux upstream is probably supporting more usecases, apparently not
yours.
[...]
I, honestly, expected someone that understand the issue to help and
chime to report it upstream.
But you didn't really explained me what the usecase was and why you
were not able to mount /proc early...
Anyway, I already reported it upstream, let's see if the come with a
patch.
