Alpine Linux in a chroot: Difference between revisions

From Alpine Linux
mNo edit summary
Line 68: Line 68:


Now you can move on to [[Creating_an_Alpine_package|creating packages for Alpine.]]
Now you can move on to [[Creating_an_Alpine_package|creating packages for Alpine.]]
== Alpine Linux in a chroot on Fedora ==
If you want to generate a chroot on a Fedora based system, you can use this [http://files.affolter-engineering.ch/alpinelinux/chroot/alpine-chroot.sh script].
{{Note|Maybe you are able to use this script on other distribution but this is not tested.}}

Revision as of 08:41, 18 June 2011

Setting up a 'edge' build environment in a chroot

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.

Introduction

You will need a few Gigabytes to have enough pace for kernel compiling and storing all the binary packages and iso image.

Create a build environment

We are setting up our Build Environment in chroot.

Note: The variables below:

  • ${build_dir} = You can name it whatever you like.
  • ${mirror} = Should be replaced with one of the available alpine-mirrors:

Choose a mirror from the mirror list.


Let's start by getting the latest apk static package:

wget http://dl-3.alpinelinux.org/alpine/v2.2/main/x86_64/apk-tools-static-2.1.0-r1.apk

Unpack the tarball

tar -xzf apk-tools-static-2.1.0-r1.apk

We are setting up a basic chroot:

mkdir ${build_dir} sudo ./sbin/apk.static -X ${mirror}/v2.2/packages/main -U --allow-untrusted --root ${build_dir} --initdb add alpine-base alpine-sdk mkdir -p ./${build_dir}/proc sudo mount --bind /proc ./${build_dir}/proc

Lets setup our needed devices:

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

seems as /dev/null is wrong

sudo rm -f ./${build_dir}/dev/null && sudo mknod -m 666 ./${build_dir}/dev/null c 1 3

We need or dns servers and root dir:

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

We are setting up apk mirrors:

sudo mkdir -p ./${build_dir}/etc/apk echo "${mirror}/v2.2/packages/main" > ./${build_dir}/etc/apk/repositories

At this point you should be able to enter your chroot:

sudo chroot ./${build_dir} /bin/sh -l

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

Now you can move on to creating packages for Alpine.

Alpine Linux in a chroot on Fedora

If you want to generate a chroot on a Fedora based system, you can use this script.

Note: Maybe you are able to use this script on other distribution but this is not tested.