Jump to content

# Offline installation

5 languages

- Čeština
- 日本語
- Português
- Русский
- 中文（简体）

From ArchWiki
Warning: Extracting the root file system image (`airootfs.sfs`) or copying the live environment's root file system is not a supported installation method. `airootfs.sfs` contains custom configuration that is not suitable or secure for an installed system.

This article provides instructions on installing Arch Linux on a system without an Internet connection. To do this, another system with a working Internet connection is required.

First, follow the Installation guide, skipping the steps requiring an internet connection (e.g. Installation guide#Connect to the internet), then continue with this guide instead of following Installation guide#Install essential packages.

## Prepare local repository

Follow Pacman/Tips and tricks#Installing packages from a CD/DVD or USB stick for instructions on preparing a local repository with the necessary files on a separate host installation.

At the very least, for a functioning system, the following packages are recommended:

    # pacman -Syw --cachedir . --dbpath /tmp/blankdb base linux linux-firmware

Tip: Consider adding other needed software, see Installation guide#Install essential packages for a list of necessary packages (like a text editor).

Create your custom offline repository:

    # repo-add ./custom.db.tar.zst ./*[^sig]

The factual accuracy of this article or section is disputed.

Reason: The command example above seems to be incorrect, cause it results in:`==> ERROR: 'some_filename.zst' is not a package file, skipping` (Discuss in Talk:Offline installation)

## Mount and configure

This article or section needs expansion.

Reason: Add optional instructions on placing the custom repo in the ISO. (Discuss in Talk:Offline installation)

Once the repository is prepared, connect the external media to the new installation, and mount it on the newly created root filesystem:

    # mount --mkdir /dev/sdxy /mnt/repo

Edit your archiso `/etc/pacman.conf` and add a new section:

    /etc/pacman.conf

    [custom]
    SigLevel = Optional
    Server = file:///mnt/repo/

Comment out `[core]` and `[extra]` so that pacman does not fail on the default repositories.

## Pacstrap

You can now continue to pacstrap your locally-available packages to the new installation:

    # pacstrap -K /mnt base linux linux-firmware

Tip: Match the packages used at #Prepare local repository in this command.

## Offline installation of packages

### Install from file

In case the offline installation process was only temporary, but requires manual installation of some packages before being able to access a network, see pacman#Additional commands to learn how to install local packages.

Shell globbing can be used to install many packages at once:

    # pacman -U /package/folder/*.tar.zst

### Offline cache

You can put the required files into `/var/lib/pacman/sync` and `/var/cache/pacman/pkg`, so as to make `pacman` think it has everything it needs to do searches, updates, and installs. The following method is based on two forum threads: [1][2].

The steps are:

1. downloading the up to date package databases on a computer with internet access,
2. transferring them to the offline computer,
3. generating the list of packages required from the offline computer to update it,
4. downloading them with their signature on a computer with internet access,
5. transferring them to the pacman cache of the offline computer,
6. installing the updates.

Tip: If you changed your default repositories from the defaults (core, extra and multilib), you should review your `/etc/pacman.conf` file.

The following script will download the updated package databases. If needed, change `MIRROR` to any mirror from the mirror status list.

    download_databases.sh

    #!/bin/sh

    ARCH="x86_64"
    MIRROR="https://mirrors.kernel.org/archlinux/"

    wget "${MIRROR}/core/os/${ARCH}/core.db"
    wget "${MIRROR}/extra/os/${ARCH}/extra.db"
    wget "${MIRROR}/multilib/os/${ARCH}/multilib.db"

    # and possibly -uncomment- (if customized in /etc/pacman.conf or pacman.conf.d):

    #wget "${MIRROR}/core-testing/os/${ARCH}/core-testing.db"
    #wget "${MIRROR}/extra-testing/os/${ARCH}/extra-testing.db"
    #wget "${MIRROR}/multilib-testing/os/${ARCH}/multilib-testing.db"

    # and -additionally- debug and staging packages.

Make the script executable and run it. You will obtain multiple .db files.

The following steps will be transferring the .db files to the offline PC, making it so you are working with up-to-date package lists (as if you ran `pacman -Sy`), then generating a list of package required for the update:

    # cp *.db /var/lib/pacman/sync/
    # pacman -Sup --noconfirm > pkglist

Note: Make sure that you have enabled at least one of the servers defined in the `/etc/pacman.d/mirrorlist` file. Otherwise, all what you get is a misleading error message: `error: no database for package: package-name`.

You will also need to download the corresponding package signatures, so prepare the list of signatures to download:

    # sed -e 's/\.zst$/.zst.sig/' ../pkglist > ../siglist

Next, bring the two lists with you to a place where you have internet and download the listed packages in an empty directory:

    # wget -nv -i ../pkglist
    # wget -nv -i ../siglist

Tip: When using cygwin or some other kind of Windows environment to download the packages, the filenames will get mangled since default Windows file naming requires to escape e.g. colons. To avoid this (under cygwin, since it does not follow such restrictions), use `wget --restrict-file-names=unix`.

Take all the `*.pkg.tar.zst` and `*.pkg.tar.zst.sig` files back home, put them in `/var/cache/pacman/pkg` and finally run:

    # pacman -Su

### Local repository

In case the new system is expected to remain offline or airgapped, it should be configured to expect only local repositories.

#### Complete repository

After chrooting into your new installation, edit the new `/etc/pacman.conf` in the same way as previously (but without the `/mnt` prefix):

    /etc/pacman.conf

    [custom]
    SigLevel = Optional
    Server = file:///repo/

Comment out all other repositories and save. Continue configuring the new system as usual.

From now on any updates to the offline system can be made by bringing an up to date copy of the local repository, mounting it to `/repo` and running pacman commands as usual.

## See also

- Help:Browsing#Offline viewing: for browsing ArchWiki offline.

Categories:

- Live Arch systems
- Installation process

Hidden categories:

- Pages or sections flagged with Template:Accuracy
- Pages or sections flagged with Template:Expansion