FakeRoot | Install fake root in termux | Hacking library

I am trying to run the following command comm -23 <(pacman -Qqe | sort) <(awk '{print $1}' /desktopfs-pkgs.txt | sort)

I get the following output

I'm buildinga a docker image using a Dockerfile to build it. I have put ARG DEBIAN_FRONTEND=noninteractive in the beginning of the Dockerfile to avoid debconf warnings while building.

The warnings does not show up when using apt-get install inside the Dockerfile. However when executing a sh script (install_dependencies.sh) from the Dockerfile that contains apt-get install commands, the warnings show up again. I also tried to set DEBIAN_FRONTEND=noninteractive inside the sh script itself.

I can solve this by adding echo 'debconf debconf/frontend select Noninteractive' | sudo debconf-set-selections in the sh script before the apt-get install commands but I would want to avoid that, since any fail in the script would leave debconf select to Noninteractive.

Dockerfile:

Context

I have a jenkins that builds a docker image for a raspberry pi 2. It is using buildx to emulate the ArmV7 environment during build. This worked great until recently I got random errors during installing the apk packages.

Dockerfile

I am having trouble packaging Sphinx v4.2 on Python v2.7.18:

I am trying to run buildroot with root user. Even after setting FORCE_UNSAFE_CONFIGURE=1 as export FORCE_UNSAFE_CONFIGURE=1 I still get configure: error: you should not run configure as root (set FORCE_UNSAFE_CONFIGURE=1 in environment to bypass this check).

When I try to run buildroot without root user I get some error related to fakeroot

Can some please guide me if running as root why even after running command export FORCE_UNSAFE_CONFIGURE=1 I still getting configure: error: you should not run configure as root (set FORCE_UNSAFE_CONFIGURE=1 in environment to bypass this check) See config.log' for more details`

How to fix it with root user so I can run buildroot

the error message also says look at the config.log file.What I like to know I ran export FORCE_UNSAFE_CONFIGURE=1 command but I could not find FORCE_UNSAFE_CONFIGURE=1 in cache variables of config.log

This is also printed in config.log

This is my process.

I start a new aws t2.micro ec2 on ubuntu20 and run this script

I wrote the code of dockerfile so it will be easier to install jenkins with all it dependencies and use it for CICD pipeline(i am using docker on windows 10). this is my code:

I have three Azure Pipeline agents built on Ubuntu 18.04 images and deployed to a Kubernetes cluster. Agents are running the latest version, 2.182.1, but this problem also happened using 2.181.0.

Executing build pipelines individually works just fine. Build completes successfully every time. But whenever a second pipeline starts while another pipeline is already running, it fails - every time - on the "Checkout" job with the following error:

The working folder U:\azp\agent\_work\1\s is already in use by the workspace ws_1_34;Project Collection Build Service (myaccount) on computer linux-agent-deployment-78bfb76d.

These are three separate and distinct agents running as separate containers. Why would a job from one container be impacting a job running on a different container? Concurrent builds work all day long on my non-container Windows servers.

The container agents are deployed as a standard Kubernetes "deployment" object:

Trying a simple python flask web app in docker 20.10.2, build 2291f61.

Doing the: docker build -t hello-world . starts out ok (please see below), but ends with: