[Bug]: frustrating AppArmor-related error `user builder is currently used by process 1`

[robertkirkman]

Problem description

Unfortunately, I have been experiencing an error that I am not sure how to reproduce, but is difficult to bypass once it starts happening:

tacokoneko@CORSAIR ~/code/termux/tur $ scripts/run-docker.sh ./build-package.sh -I -f gcc-15
Running container 'tur-termux-package-builder' from image 'ghcr.io/termux/package-builder'...
WARNING: apparmor_parser not found, AppArmor profiles will not be loaded!
         This is not recommended, as it may cause security issues and unexpected behavior
         Avoid executing untrusted code in the container
Creating new container...
df1a8650290083aa0e9295989b9484a84faba0c743211ecd0cdec061922811d7
Changed builder uid/gid... (this may take a while)
usermod: user builder is currently used by process 1
tacokoneko@CORSAIR ~/code/termux/tur $ 

It bisects to this, so I would like to apply a more complete condensed reversion of this PR that I have developed and tested:

• ci: use fuse-overlayfs to reduce runtime storage used by builder termux/termux-packages#28602

This is also related to this:

• chore(common-files/building-system-patches): remove do-not-use-python-from-usr-bin.patch #2296

Unfortunately, I did not completely finish that PR before it was merged, so I will work on a more complete version now.

This is also related to this:

• [Bug]: termux-am fails to build after the enablement of AppArmor termux/termux-packages#29118

Deleting the container and even deleting all containers and images and trying again does not help the problem once it has started, nor does restarting the computer:

docker container kill termux-package-builder
docker container rm termux-package-builder
# remove any other containers also using the termux/package-builder image
docker container rm other-termux-package-builder other2-termux-package-builder
for c in $(docker container ls -a --format "table {{.Names}}" | grep termux-package-builder); do docker container rm $c; done
docker image prune -a
# like sudo systemctl restart docker
sudo rc-service docker restart
sudo reboot

There may be an unknown factor required to reproduce it, but my patch can prevent it and it also can fix it once it has started happening

https://github.com/robertkirkman/termux-generator/blob/54be8e4f18c5ed4eb82cb9a9e7fe09db92b953de/play-store-patches/bootstrap-patches/docker-fixes.patch

What steps will reproduce the bug?

1. Build some TUR packages using regular commands (this is the command I was using for a while before the problem happened):

git clone https://github.com/termux-user-repository/tur.git
cd tur
./setup-environment.sh
scripts/run-docker.sh ./build-package.sh -I -f -a i686 python-tokenizers

2. Wait about 20 hours, then use these commands (I used these immediately before the problem started today):

git pull origin master
./setup-environment.sh
scripts/run-docker.sh ./build-package.sh -I -f gcc-15

What is the expected behavior?

Reliable behavior of termux-package-builder in TUR without the error usermod: user builder is currently used by process 1 occurring

System information

termux-info:

N/A