diff options
author | Eli Schwartz <eschwartz@archlinux.org> | 2023-04-11 12:42:36 -0400 |
---|---|---|
committer | Eli Schwartz <eschwartz@archlinux.org> | 2023-04-14 15:13:12 -0400 |
commit | 3bc2236c59249f44f20f8b52ddcd7a44938ea2f0 (patch) | |
tree | b75cadd0b3a3a78003062d9d823f79d9cdf4b7d3 /docs/refman/loaderyaml.py | |
parent | 9a77c45e4192df1b89a3631aa3ce379922c4bf5c (diff) | |
download | meson-3bc2236c59249f44f20f8b52ddcd7a44938ea2f0.zip meson-3bc2236c59249f44f20f8b52ddcd7a44938ea2f0.tar.gz meson-3bc2236c59249f44f20f8b52ddcd7a44938ea2f0.tar.bz2 |
minstall: work around broken environments with missing UIDs
Running some container-like mechanisms such as chroot(1) from sudo, can
result in a new isolated environment where the environment variables
exist but no users exist. From there, a build is performed as root but
installation fails when we try to look up the passwd database entry for
the user outside of the chroot.
Proper container mechanisms such as systemd-nspawn, and even improper
ones like docker, sanitize this and ensure those stale environment
variables don't exist anymore. But chroot is very low-level.
Avoid crashing when this happens.
Fixes #11662
Diffstat (limited to 'docs/refman/loaderyaml.py')
0 files changed, 0 insertions, 0 deletions