Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#56622 - {arch-install-scripts} arch-chroot doesn't fix /proc after unshare --pid

Attached to Project: Arch Linux
Opened by Yuxuan Shui (yshui) - Thursday, 07 December 2017, 16:45 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 14 December 2017, 18:18 GMT
Task Type Bug Report
Category Arch Projects
Status Assigned
Assigned To Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Trying to interact with PIDs outside the namespace will just fail, while 'ps' still shows those processes.

On the other hand, it's impossible to query information about processes inside the namespace, it's really hard to find the correct PID to, say, kill a process.

Some applications that relies on /proc might also fail.
This task depends upon

Comment by Dave Reisner (falconindy) - Thursday, 07 December 2017, 18:49 GMT
What are you doing in the chroot that this matters? arch-chroot wasn't meant for long running tasks -- just an easy way of sneaking into the chroot for initial setup. You could just as easily use systemd-nspawn instead, and that probably gives you the feature you're looking for.
Comment by Yuxuan Shui (yshui) - Friday, 08 December 2017, 10:37 GMT
If that's the case, why do we use --pid at all?
Comment by Dave Reisner (falconindy) - Friday, 08 December 2017, 12:22 GMT

Loading...