Am 25.01.23 um 10:15 schrieb Polarian:
I ran into a small issue, there is "no available disk space" if this is not done on its own partition, aka if you do not mount a partition to the chroot.
Is there any method without having to partition up my disk to allocate storage to a chroot, as currently it has no root storage...
All you need is a directory to store the files of your build environment. Of course the filesystem this directory lives in needs enough free space to hold a minimal Arch installation, which is about 3 GBytes. If the system, you want to try this on, is short of storage, and / is a filesystem that supports reflinks (btrfs and newest xfs), you could snapshot or reflink all files of your running system into the new build-root (skipping pacstrap) # btrfs subvolume snapshot / build-root or # cd / # mkdir build-root # cp --reflink=always -ax /{bin,lib,var,etc,lib64,root,sbin,usr} build-root/ # mkdir -p build-root/{boot,dev,home,opt,proc,run,srv,sys,tmp} then, after chroot-ing into it, use pacman to uninstall everything that is not a dependency of base or base-devel. I did something similar to clean up a machine: # arch-chroot build-root /bin/bash # cd /tmp # pactree -u base | sed 's/[<>=].*$//' | sort -u > base.deps # pacman -Qg base-devel | cut -d' ' -f2 | sort -u > base-devel.deps # sort -um base.deps base-devel.deps > clean-pkgs # pacman -Qe | cut -d' ' -f1 | sort -u > current-pkgs After that, # diff --suppress-common-lines clean-pkgs current-pkgs | sed -n 's/^> //p' | pacman -Rcsn - would uninstall everything that does not belong to base or base-devel. Base-devel.deps is a bit misleading, it does not contain all dependencies, but as only explicit packages are uninstalled later, this seems to work alright. I am not implying that this would be my preferred course of action, but it is fast and space efficient. Next time you write about a problem you ran into, better show everything you did and the error message you got, using copy and paste. BR