DeveloperWiki talk:Building in a clean chroot

From ArchWiki
Latest comment: 09:35 by Gcb in topic More info needed RE: archbuild

Deleting a chroot

It's not written in the page so I'll write it here: Just delete the $CHROOT folder (Unless it's btrfs). Tharbad (talk) 03:05, 12 May 2019 (UTC)Reply[reply]

More info needed RE: archbuild

With the semi-recent changes to chroot building and the addition of the archbuild convenience script, using a custom repo within your build chroot is no longer supported. It is therefore required to create (or symlink) a pacman.conf to /usr/share/devtools/pacman-<some_name>.conf, and then run <some_name>-x86_64-build to build packages in a chroot that will have access to your custom repo.

For more background, see this reddit post and this response thread.

Terminalmage (talk) 01:39, 10 December 2019 (UTC)Reply[reply]

updating this comment from 2019... I think this page needs an update by someone more familiar with devtool package. Mainly a note about arch-nspawn usage/sideeffects over chroot. Gcb (talk) 09:35, 22 May 2024 (UTC)Reply[reply]

Note about BTRFS subvolumes

There is a note attached underneath the first `mkarchchroot` command that says:

On btrfs, the chroot is created as a subvolume, so you have to remove it by removing the subvolume by running btrfs subvolume delete $CHROOT/root as root.

According to this: , BTRFS subvolumes can just be removed normally with `rmdir` or `rm`. Should this note be removed?

—This unsigned comment is by Saltedcoffii (talk) 2022-11-21T13:29:06. Please sign your posts with ~~~~!

Troubleshooting: no space left on device

During build with Classic Way for larger source code, you may encounter error "no space left on device". One of the solution is to mount the host /tmp,

$ makechrootpkg -d /tmp -r $CHROOT

Ms (talk) 17:03, 16 February 2023 (UTC)Reply[reply]

And then you will most likely run out of RAM rather than disk space... — Lahwaacz (talk) 15:23, 8 March 2023 (UTC)Reply[reply]

Closing old discussion. — Lahwaacz (talk) 07:50, 23 March 2024 (UTC)Reply[reply]

Adjusted mirrorlist can be over written when up dating the chroot

Quoting the end of 3.1 Setting up a chroot

Also adjust the mirrorlist in $CHROOT/root/etc/pacman.d/mirrorlist

Quoting the beginning of 3.2 Building in the chroot

Firstly, make sure the base chroot ($CHROOT/root) is up to date:
$ arch-nspawn $CHROOT/root pacman -Syu

Depending on the configuration, the adjusted mirrorlist can be over written when making sure the base chroot is up to date. Should the article point out the possible over write?

Regid (talk) 15:39, 18 March 2023 (UTC)Reply[reply]