In order to fix a recent issue, an update has been added to Portage in order to check for /run being a mounted directory. Is there any reason for it to be mounted instead of just being an existing directory? I understand that /run is tmpfs normally. But this check does trigger a warning if Gentoo is being used inside Docker where /run is not a tmpfs directory unless specifically added as a volume. The warning message: !!! It seems /run is not mounted. Process management may malfunction. I am not seeing /run used as a mounted volume in most Docker environments. So using Gentoo / Portage in Docker does no longer work like one would expect, without a permanent warning or a pretty uncommon /run volume. Would it be possible to change this check to be less restrictive? This is the related issue: https://bugs.gentoo.org/816303 The commit in question: https://gitweb.gentoo.org/proj/portage.git/commit/?id=0e9e12aadb889766d61c0561b9723e71542d43e6 Reproducible: Always
/run should definitely be mounted in a container environment. If docker doesn't do that by default, it really should.
That said, we ended up fixing build-docbook-catalog in a different way (it now creates locks in /etc/xml), so we could potentially revert 0e9e12aadb889766d61c0561b9723e71542d43e6 without causing any known breakage.
Well, i am not sure if we should expect the Docker devs to change the default behaviour of /run. There are options to mount it if required. But it would need additional parameters, as outlined here: https://docs.docker.com/storage/tmpfs
(In reply to Mike Gilbert from comment #2) > That said, we ended up fixing build-docbook-catalog in a different way (it > now creates locks in /etc/xml), so we could potentially revert > 0e9e12aadb889766d61c0561b9723e71542d43e6 without causing any known breakage. +1 to revert this check. It seems pretty useless and annoying to me. :-)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=1327fa9f829e8670c65ff35b9b0bda446991f7ed commit 1327fa9f829e8670c65ff35b9b0bda446991f7ed Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2022-02-14 20:30:18 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-02-14 21:50:55 +0000 Revert "lib/_emerge/actions.py: warn on missing /run" Portage itself does not need /run to be mounted. build-docbook-catalog was adjusted to create locks in /etc/xml instead. Bug: https://bugs.gentoo.org/832853 Reverts: 0e9e12aadb889766d61c0561b9723e71542d43e6 Signed-off-by: Mike Gilbert <floppym@gentoo.org> Closes: https://github.com/gentoo/portage/pull/788 Signed-off-by: Sam James <sam@gentoo.org> lib/_emerge/actions.py | 33 ++++++++++++--------------------- 1 file changed, 12 insertions(+), 21 deletions(-)
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bb044a3dd58f5d6ac0fa66dfe07daf3c6773480e commit bb044a3dd58f5d6ac0fa66dfe07daf3c6773480e Author: Sam James <sam@gentoo.org> AuthorDate: 2022-04-15 08:35:57 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-04-15 08:36:54 +0000 sys-apps/portage: backport new QA checks; /run warning removal portage.git is currently undergoing a fair bit of refactoring and other non-trivial changes, so let's backport some useful bits. - Backport QA checks (eend w/o ebegin, ebegin w/o eend, /var/tmp install dir) - Drop obsolete /run-not-mounted warning Bug: https://bugs.gentoo.org/835824 Bug: https://bugs.gentoo.org/835823 Bug: https://bugs.gentoo.org/832853 Bug: https://bugs.gentoo.org/493154 Bug: https://bugs.gentoo.org/837536 Signed-off-by: Sam James <sam@gentoo.org> sys-apps/portage/files/3.0.30-qa-checks.patch | 137 ++++++++++ .../portage/files/3.0.30-revert-run-warn.patch | 64 +++++ sys-apps/portage/portage-3.0.30-r2.ebuild | 276 +++++++++++++++++++++ 3 files changed, 477 insertions(+)
