Bug 832043

Summary:	>=sys-apps/portage-3.0.29 claims there is no /run mounted when run in a chroot
Product:	Gentoo Linux	Reporter:	tt_1 <herrtimson>
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	output from emerge --info

Description tt_1 2022-01-25 14:19:09 UTC

so I just noticed this while chrooting and compiling stuff: when upgrading portage from 3.0.28-r1 to 3.0.29 or newer, there is a strong warning about not mounted /sys 

emerge -av rust-bin -1
!!! It seems /run is not mounted. Process management may malfunction.

it seems to happen only when inside a chroot. 

here is how I setup mine: 

mount -o loop var/portage/portage.sqfs usr/portage/
mount -t proc none proc/
mount --rbind /dev dev/
mount --rbind /sys sys/

screen chroot . /bin/bash
followed by 
source /etc/profile
env-update

from outside of the chroot, sys/ is mounted all the way:

ls sys/
block  bus  class  dev  devices  firmware  fs  kernel  module  power

and so is from within the chrooted dir:

ls /sys/
block  bus  class  dev  devices  firmware  fs  kernel  module  power


however, if I fire up portage, it gives out the aforementioned warning: 

!!! It seems /run is not mounted. Process management may malfunction.

current workaround: downgrade portage to portage-3.0.28-r1 

note: this is an openrc system, and I believe this is a false positive. 

Tried to diff the tarballs of portage-3.0.28 and portage-3.0.29, but was unable to see an obvious problem.

Comment 1 tt_1 2022-01-25 14:20:58 UTC

Created attachment 763610 [details]
output from emerge --info

Comment 2 tt_1 2022-01-25 14:36:01 UTC

whops, I managed to read /sys instead of /run. 

mount --rbind /run makes portage silence the warning