Alpine Linux in a chroot: Difference between revisions

From Alpine Linux
(simplify extraction of apk.static)
(use bash, separate initialization runlevel, make note about install are not boot able)
(22 intermediate revisions by 8 users not shown)
Line 1: Line 1:
This document explains how to set up an Alpine build environment in a chroot under a "normal" Linux distro, such as Arch, Debian, Fedora, Gentoo, or Ubuntu. Once inside the chroot environment, you can build, debug, and run alpine packages. The guide can also be used to install Alpine Linux from a non-Alpine Linux livecd such as Ubuntu or System rescue CD.
Inside the chroot environment, you can build, debug, and run alpine packages or develop things. It's the most knowed way to do so if not wants to trash your main Alpine system.
This example installation of Alpine Linux in a chroot will work with the lastest release. But it's also possible to make a chroot with '''[[Edge|edge]]''' or older releases of Alpine Linux to test backports.
 
This document explains how to set up an [[Alpine_newbie#Developer|Alpine build environment]] in a chroot under a host Linux distro, can also be used to install Alpine Linux from a non-Alpine Linux livecd.


== Requirements ==
== Requirements ==
For the base Alpine Linux you will only need around 6MB of free space; though to build packages you'll need at least 500 MB.
 
* Working Linux instalation where to perform all the process
* Linux kernel 2.6.22, with <code>wget</code> and <code>chroot</code> installed
* target media with at least 100M, 900MB for more complete solution as minimum
* internet connection


== Prerequisites ==
== Prerequisites ==
The variables below:  
The variables below:  


*'''${chroot_dir}''' = Should point to the chroot directory where you  
*'''${chroot_dir}''' = Should point to the chroot directory where you  
*'''${mirror}''' = Should be replaced with [http://dl-2.alpinelinux.org/alpine/MIRRORS.txt one of the available Alpine Linux mirrors].
*'''${mirror}''' = Should be replaced with [http://nl.alpinelinux.org/alpine/MIRRORS.txt one of the available Alpine Linux mirrors].
*'''${arch}''' =  Should be the cpu architecture like x86 (i386) or amd64(x86_64)..


== Set up APK ==
== Set up APK ==


Download the latest apk static package:
Download the latest apk static package (replace <tt>${version}</tt> with actual version):
 
{{Tip|In the command below, replace x86_64 with x86 if running on a 32 bit installation}}
 
{{Warning|You will need Kernel version 2.6.22 or later to use apk-tools-static}}


{{Cmd|wget ${mirror}/v3.0/main/x86_64/apk-tools-static-2.4.4-r0.apk}}
{{Cmd|wget ${mirror}/latest-stable/main/${arch}/apk-tools-static-${version}.apk}}


.apk packages are just gzipped tarballs, unpack using:
.apk packages are just gzipped tarballs, unpack using:
{{Cmd|tar -xzf apk-tools-static-2.4.4-r0.apk sbin/apk.static}}
{{Cmd|tar -xzf apk-tools-static-*.apk}}


== Install the alpine base installation onto the chroot ==
== Install the alpine base installation onto the chroot ==


{{Cmd|./sbin/apk.static -X ${mirror}/v3.0/main -U --allow-untrusted --root ${chroot_dir} --initdb add alpine-base}}
{{Cmd|./sbin/apk.static -X ${mirror}/latest-stable/main -U --allow-untrusted --root ${chroot_dir} --initdb add alpine-base}}


== Set up the chroot ==
== Set up the chroot ==


Set up some devices in the chroot
Before made and enter into the chrooted system must be prepared with device nodes and tempfs :
{{Tip|Manually creating devices is not needed if you choose to mount /dev of the hosts in the chroot described later.}}
 
===== Method 1.A fast way: using bind mount =====
 
{{Note|Mounts with bind, can mount in read-only the /dev at the alpine chroot so due limited will not touch the  access time of the host system}}
 
{{Cmd|mount /dev/ /alpine/dev/ --bind
mount -o remount,ro,bind /alpine/dev
}}
 
If you need SCSI or R/W access only do the first command, mounting with "ro" makes more secure your chroot.
 
===== Method 1.B manual way: creating need nodes =====
 
{{Warning|Manually creating devices will only provide those representation that you have created.. for auto availability use bind mounts}}


{{Cmd|mknod -m 666 ${chroot_dir}/dev/full c 1 7
{{Cmd|mknod -m 666 ${chroot_dir}/dev/full c 1 7
Line 50: Line 66:
mknod -m 666 ${chroot_dir}/dev/sda6 b 8 6
mknod -m 666 ${chroot_dir}/dev/sda6 b 8 6
mknod -m 666 ${chroot_dir}/dev/sdb b 8 16
mknod -m 666 ${chroot_dir}/dev/sdb b 8 16
mknod -m 666 ${chroot_dir}/dev/sda1 b 8 17
mknod -m 666 ${chroot_dir}/dev/sdb1 b 8 17
mknod -m 666 ${chroot_dir}/dev/sda2 b 8 18
mknod -m 666 ${chroot_dir}/dev/sdb2 b 8 18
mknod -m 666 ${chroot_dir}/dev/sda3 b 8 19
mknod -m 666 ${chroot_dir}/dev/sdb3 b 8 19
mknod -m 666 ${chroot_dir}/dev/sda4 b 8 20
mknod -m 666 ${chroot_dir}/dev/sdb4 b 8 20
mknod -m 666 ${chroot_dir}/dev/sda5 b 8 21
mknod -m 666 ${chroot_dir}/dev/sdb5 b 8 21
mknod -m 666 ${chroot_dir}/dev/sda6 b 8 22}}
mknod -m 666 ${chroot_dir}/dev/sdb6 b 8 22}}
 
==== Made available proc and sys fs ====
 
{{Cmd|mount -t proc none ${chroot_dir}/proc
mount -o bind /sys ${chroot_dir}/sys}}
 
==== Make networking resolution access ====


A resolv.conf is needed for name resolution:  
A resolv.conf is needed for name resolution:  
Line 62: Line 85:
mkdir -p ${chroot_dir}/root}}
mkdir -p ${chroot_dir}/root}}


If you don't want to copy the resolv.conf from the local machine, you can create a new one using Googles DNS servers:  
If you don't want to copy the resolv.conf from the local machine, you can create a new one using OpenDNS servers (or any other):  
{{Cmd|echo 'nameserver 8.8.8.8' > ${chroot_dir}/etc/resolv.conf}}
{{Cmd|echo -e 'nameserver 8.8.8.8\nnameserver 2620:0:ccc::2' > ${chroot_dir}/etc/resolv.conf}}
 
==== prepare the apk sources software ====


Set up APK mirror:
Set up APK mirror (replace <tt>${branch}</tt> with the latest stable branch name, e.g. v3.3):


{{Cmd|mkdir -p ${chroot_dir}/etc/apk
{{Cmd|mkdir -p ${chroot_dir}/etc/apk
echo "${mirror}/v3.0/main" > ${chroot_dir}/etc/apk/repositories}}
echo "${mirror}/${branch}/main" > ${chroot_dir}/etc/apk/repositories}}


== Entering your chroot ==
== Entering your chroot ==
At this point, Alpine has been succesfully installed onto the chroot directory. Before you chroot in you
will probably want to mount /proc and /sys in the chroot:


{{Cmd|mount -t proc none ${chroot_dir}/proc
{{Warning|At this point, Alpine has been succesfully installed onto the chroot directory '''but still not able to boot it'''. }}
mount -o bind /sys ${chroot_dir}/sys}}
 
{{Cmd|chroot ${chroot_dir} /bin/bash -l}}
 
==== Perform init process ====
 
Need to add some minimal initscripts to appropriate runlevels:
 
{{Cmd|rc-update add devfs sysinit
rc-update add dmesg sysinit
rc-update add mdev sysinit
 
rc-update add hwclock boot
rc-update add modules boot
rc-update add sysctl boot
rc-update add hostname boot
rc-update add bootmisc boot
rc-update add syslog boot
 
rc-update add mount-ro shutdown
rc-update add killprocs shutdown
rc-update add savecache shutdown}}


If you don't want to create special device files yourself, mount the hosts device directory onto the chroot:
{{Cmd|mount -o bind /dev ${chroot_dir}/dev}}


You can now chroot:
= Troubleshooting =
{{Cmd|chroot ${chroot_dir} /bin/sh -l}}


Alpine Linux has a great meta-package for building Alpine packages from source available called alpine-sdk. To install, run:
== hardened kernels or alpine as chroot host ==
{{Cmd|apk add alpine-sdk}}


If you are using Alpine as a Native build system you will have to make sure that chroot can run chmod. Add following to /etc/sysctl.conf
If you are using Alpine as a Native build system you will have to make sure that chroot can run chmod. Add following to <code>/etc/sysctl.conf</code>


kernel.grsecurity.chroot_deny_chmod = 0
<code>kernel.grsecurity.chroot_deny_chmod = 0</code>


Then run the following command
Then run the following command


{{Cmd|sysctl -p}}
<code>sysctl -p</code>
 


== Alpine Linux in a chroot on Fedora ==
== chroot: cannot run command ' ... Exec format error ==


If you want to generate a chroot on a Fedora based system, you can use this [http://git.alpinelinux.org/cgit/fab/scripts/tree/alpine-chroot.sh script].
This usually indicates that you booted with one architecture (e.g. armf) and are trying to chroot into another (e.g. x86_64). If you plans to make chroot into another installation must use same arch for both host and hosted chrooted!


{{Note|Maybe you are able to use this script on other distribution but this is not tested.}}
Note that with '''one exception you can run 32 bit x86 chroot in x86_64, but not viceversa'''!


= Troubleshooting =
== WARNING: Ignoring APKINDEX.xxxx.tar.gz ==
== WARNING: Ignoring APKINDEX.xxxx.tar.gz ==
Make sure ${chroot_dir}/etc/apk/repositories is valid and inside the chroot run:
 
{{Cmd|apk update}}
Make sure <code>${chroot_dir}/etc/apk/repositories</code> is valid and inside the chroot run:
 
<code>apk update</code>
 
= External links =
 
* You can also use script [https://github.com/alpinelinux/alpine-chroot-install/ alpine-chroot-install]
* https://web.archive.org/web/20190808203313/https://isc.sans.edu/forums/diary/Forensic+use+of+mount+bind/22854/
* Alpine Linux in a chroot on Fedora : http://git.alpinelinux.org/cgit/user/fab/scripts/tree/alpine-chroot.sh script
* Alpine Linux aarch64 in a chroot on AWS Linux : https://gist.github.com/emolitor/0567e51c0ce04f4b025fc78d2cf0b4f1 script


[[Category:Installation]]
[[Category:Installation]]

Revision as of 19:38, 15 August 2019

Inside the chroot environment, you can build, debug, and run alpine packages or develop things. It's the most knowed way to do so if not wants to trash your main Alpine system.

This document explains how to set up an Alpine build environment in a chroot under a host Linux distro, can also be used to install Alpine Linux from a non-Alpine Linux livecd.

Requirements

  • Working Linux instalation where to perform all the process
  • Linux kernel 2.6.22, with wget and chroot installed
  • target media with at least 100M, 900MB for more complete solution as minimum
  • internet connection

Prerequisites

The variables below:

  • ${chroot_dir} = Should point to the chroot directory where you
  • ${mirror} = Should be replaced with one of the available Alpine Linux mirrors.
  • ${arch} = Should be the cpu architecture like x86 (i386) or amd64(x86_64)..

Set up APK

Download the latest apk static package (replace ${version} with actual version):

wget ${mirror}/latest-stable/main/${arch}/apk-tools-static-${version}.apk

.apk packages are just gzipped tarballs, unpack using:

tar -xzf apk-tools-static-*.apk

Install the alpine base installation onto the chroot

./sbin/apk.static -X ${mirror}/latest-stable/main -U --allow-untrusted --root ${chroot_dir} --initdb add alpine-base

Set up the chroot

Before made and enter into the chrooted system must be prepared with device nodes and tempfs :

Method 1.A fast way: using bind mount
Note: Mounts with bind, can mount in read-only the /dev at the alpine chroot so due limited will not touch the access time of the host system

mount /dev/ /alpine/dev/ --bind mount -o remount,ro,bind /alpine/dev

If you need SCSI or R/W access only do the first command, mounting with "ro" makes more secure your chroot.

Method 1.B manual way: creating need nodes
Warning: Manually creating devices will only provide those representation that you have created.. for auto availability use bind mounts


mknod -m 666 ${chroot_dir}/dev/full c 1 7 mknod -m 666 ${chroot_dir}/dev/ptmx c 5 2 mknod -m 644 ${chroot_dir}/dev/random c 1 8 mknod -m 644 ${chroot_dir}/dev/urandom c 1 9 mknod -m 666 ${chroot_dir}/dev/zero c 1 5 mknod -m 666 ${chroot_dir}/dev/tty c 5 0

If you need SCSI disc access:

mknod -m 666 ${chroot_dir}/dev/sda b 8 0 mknod -m 666 ${chroot_dir}/dev/sda1 b 8 1 mknod -m 666 ${chroot_dir}/dev/sda2 b 8 2 mknod -m 666 ${chroot_dir}/dev/sda3 b 8 3 mknod -m 666 ${chroot_dir}/dev/sda4 b 8 4 mknod -m 666 ${chroot_dir}/dev/sda5 b 8 5 mknod -m 666 ${chroot_dir}/dev/sda6 b 8 6 mknod -m 666 ${chroot_dir}/dev/sdb b 8 16 mknod -m 666 ${chroot_dir}/dev/sdb1 b 8 17 mknod -m 666 ${chroot_dir}/dev/sdb2 b 8 18 mknod -m 666 ${chroot_dir}/dev/sdb3 b 8 19 mknod -m 666 ${chroot_dir}/dev/sdb4 b 8 20 mknod -m 666 ${chroot_dir}/dev/sdb5 b 8 21 mknod -m 666 ${chroot_dir}/dev/sdb6 b 8 22

Made available proc and sys fs

mount -t proc none ${chroot_dir}/proc mount -o bind /sys ${chroot_dir}/sys

Make networking resolution access

A resolv.conf is needed for name resolution:

cp /etc/resolv.conf ${chroot_dir}/etc/ mkdir -p ${chroot_dir}/root

If you don't want to copy the resolv.conf from the local machine, you can create a new one using OpenDNS servers (or any other):

echo -e 'nameserver 8.8.8.8\nnameserver 2620:0:ccc::2' > ${chroot_dir}/etc/resolv.conf

prepare the apk sources software

Set up APK mirror (replace ${branch} with the latest stable branch name, e.g. v3.3):

mkdir -p ${chroot_dir}/etc/apk echo "${mirror}/${branch}/main" > ${chroot_dir}/etc/apk/repositories

Entering your chroot

Warning: At this point, Alpine has been succesfully installed onto the chroot directory but still not able to boot it.


chroot ${chroot_dir} /bin/bash -l

Perform init process

Need to add some minimal initscripts to appropriate runlevels:

rc-update add devfs sysinit rc-update add dmesg sysinit rc-update add mdev sysinit rc-update add hwclock boot rc-update add modules boot rc-update add sysctl boot rc-update add hostname boot rc-update add bootmisc boot rc-update add syslog boot rc-update add mount-ro shutdown rc-update add killprocs shutdown rc-update add savecache shutdown


Troubleshooting

hardened kernels or alpine as chroot host

If you are using Alpine as a Native build system you will have to make sure that chroot can run chmod. Add following to /etc/sysctl.conf

kernel.grsecurity.chroot_deny_chmod = 0

Then run the following command

sysctl -p


chroot: cannot run command ' ... Exec format error

This usually indicates that you booted with one architecture (e.g. armf) and are trying to chroot into another (e.g. x86_64). If you plans to make chroot into another installation must use same arch for both host and hosted chrooted!

Note that with one exception you can run 32 bit x86 chroot in x86_64, but not viceversa!

WARNING: Ignoring APKINDEX.xxxx.tar.gz

Make sure ${chroot_dir}/etc/apk/repositories is valid and inside the chroot run:

apk update

External links