- Start an interactive shell (
bash, by default) in a new root directory:
- Specify the user (other than the current user) to run the shell as:
arch-chroot -u user path/to/new/root
- Run a custom command (instead of the default
bash) in the new root directory:
arch-chroot path/to/new/root command command_arguments
- Specify the shell, other than the default
bash(in this case, the
zshpackage should have been installed in the target system):
arch-chroot path/to/new/root zsh
arch-chroot [options] chroot-dir [command] [arguments...]
arch-chroot wraps the chroot(1) command while ensuring that important functionality is available, e.g. mounting /dev/, /proc and other API filesystems, or exposing resolv.conf(5) to the chroot.
If command is unspecified, arch-chroot will launch /bin/bash.
The target chroot-dir should be a mountpoint. This ensures that tools such as pacman(8) or findmnt(8) have an accurate hierarchy of the mounted filesystems within the chroot. If your chroot target is not a mountpoint, you can bind mount the directory on itself to make it a mountpoint, i.e.:
mount --bind /your/chroot /your/chroot
Run in unshare mode. This will use unshare(1) to create a new mount and user namespace, allowing regular users to create new system installations.
- -u <user>[:group]
Specify non-root user and optional group to use.
Output syntax and command line options.
Bugs can be reported on the bug tracker https://bugs.archlinux.org in the Arch Linux category and title prefixed with [arch-install-scripts] or via firstname.lastname@example.org.
- Dave Reisner <email@example.com>
- Eli Schwartz <firstname.lastname@example.org>
For additional contributors, use git shortlog -s on the arch-install-scripts.git repository.