test report: CentOS 7 related distro

[starsareintherose]

First it will show

junest -f
environment: line 1: /usr/bin/which: No such file or directory
fakeroot: preload library `libfakeroot.so' not found, aborting.

junest proot -f
sh-5.1# sudo pacman -Syu
fakeroot: preload library `libfakeroot.so' not found, aborting.

After adding which, then

junest -f
fakeroot internal error #43: Identifier removed
semop(2): encountered an error: Invalid argument
/usr/bin/fakeroot: line 1: kill: (119) - No such process

OS information

• rocky

  cat /etc/os-release 
  NAME="Rocky Linux"
  VERSION="8.7 (Green Obsidian)"
  ID="rocky"
  ID_LIKE="rhel centos fedora"
  VERSION_ID="8.7"
  PLATFORM_ID="platform:el8"
  PRETTY_NAME="Rocky Linux 8.7 (Green Obsidian)"
  ANSI_COLOR="0;32"
  LOGO="fedora-logo-icon"
  CPE_NAME="cpe:/o:rocky:rocky:8:GA"
  HOME_URL="https://rockylinux.org/"
  BUG_REPORT_URL="https://bugs.rockylinux.org/"
  ROCKY_SUPPORT_PRODUCT="Rocky-Linux-8"
  ROCKY_SUPPORT_PRODUCT_VERSION="8.7"
  REDHAT_SUPPORT_PRODUCT="Rocky Linux"
  REDHAT_SUPPORT_PRODUCT_VERSION="8.7"

• amazon

  
  NAME="Amazon Linux"
  VERSION="2023"
  ID="amzn"
  ID_LIKE="fedora"
  VERSION_ID="2023"
  PLATFORM_ID="platform:al2023"
  PRETTY_NAME="Amazon Linux 2023"
  ANSI_COLOR="0;33"
  CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2023"
  HOME_URL="https://aws.amazon.com/linux/"
  BUG_REPORT_URL="https://github.com/amazonlinux/amazon-linux-2023"
  SUPPORT_END="2028-03-01"

- SL 7

NAME="Scientific Linux" VERSION="7.9 (Nitrogen)" ID="scientific" ID_LIKE="rhel centos fedora" VERSION_ID="7.9" PRETTY_NAME="Scientific Linux 7.9 (Nitrogen)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:scientificlinux:scientificlinux:7.9:GA" HOME_URL="http://www.scientificlinux.org//" BUG_REPORT_URL="mailto:scientific-linux-devel@listserv.fnal.gov"

REDHAT_BUGZILLA_PRODUCT="Scientific Linux 7" REDHAT_BUGZILLA_PRODUCT_VERSION=7.9 REDHAT_SUPPORT_PRODUCT="Scientific Linux" REDHAT_SUPPORT_PRODUCT_VERSION="7.9"

[fsquillace]

libfakeroot.so is supposed to be in junest itself. I am wondering whether LD_LIBRARY_PATH is somewhat modified before running junest?

I cannot reproduce the issue.

Here is the command that junest run: https://github.com/fsquillace/junest/blob/master/lib/core/namespace.sh#LL110C136-L110C141

The sudo is a modified version which invokes fakechroot within the junest environment, so in theory libfakeroot.so should exist: https://github.com/fsquillace/junest-aur-repo/blob/master/pkgs/sudo-fake/PKGBUILD#L61

[starsareintherose]

yeah, it should have, I use docker img to generate a new junest img, this is the link https://repo.bioarchlinux.org/junest/bioarchlinux-junest.tar.gz , is official img work well under them?

this is the build script https://github.com/BioArchLinux/junest-img/blob/main/Dockerfile

[fsquillace]

I'd expect that the official image should work correctly. not sure I understand the dockerfile. how does the bioarchlinux contain junest packages? are we sure sudo-fake gets installed correctly (the package conflicts with the original sudo so sudo should not be installed).

[starsareintherose]

yeah, sudo-fake is installed, bubblewrap git groot junest proot qemu-user-static yay which are also installed, as well, /etc/junest/info contains the content reading JUNEST_ARCH=x86_64