Alpine Linux - User contributions [en]

APKBUILD examples:Go

2020-05-26T07:05:42Z

Votsalo: typo correction

== Go package policies ==

Go previous to version 1.6 did not handle dependencies ([https://github.com/golang/go/wiki/PackageManagementTools very well]).
Every package inside alpine aports should be made reproducible (aka [https://reproducible-builds.org/ reproducible builds]). Many Go projects still do not support proper verdoring and will pull all its depends from master branches. Because of this, packages made in different time spans could differ from each other (they are not bit to bit equal). We can prevent this if the source from which we build will always be the same (hence we use checksums to verify source tarballs which we fetch from upstream projects).

We currently have 3 situations a Go packages could belong to:

# A package has no vendor directory (or is empty).
# A package has a vendor directory and contains a vendor file.
# A package has a vendor directory has a vendor file but also includes all deps.

TODO:
write something about glide for #1

write something about glide or another pkg manager for #2

just do go build for #3

Allow stripping of go bins https://github.com/golang/go/issues/1242

[[Category:Development]]

Install Alpine on LXD

2019-01-18T09:26:28Z

Votsalo:

== LXD ==

LXD is an easy to use daemon and client for managing LXC containers. It is included by default in Ubuntu 16.04 and later versions. It may become available in other distributions, such as debian. If you are not familiar at all with LXC or LXD, start directly with LXD. For detailed instructions on how to use it, see https://linuxcontainers.org/lxd/introduction/

With LXD you can start an Alpine Linux container in seconds, in practically any Ubuntu 16.04 (or later) system, including:
* A standalone system
* An Amazon EC2 instance
* An OpenStack KVM VPS

With LXD, you can easily run Alpine in all those environments, on top of an Ubuntu Host.

These instructions assume you are running on an amd64 (x86_64) platform.

== LXD installation ==
On Ubuntu 18.04 there are two versions of LXD available:
* From apt packages, included by default on a new installation
* From snap. The snap version of LXD has a higher version and more features than the apt version. Future versions of LXD will be distributed only via snap.

If you want to use the latest LXD, remove the apt version and install the snap version:
{{Cmd|sudo apt-get remove lxd lxd-client
sudo snap install lxd
}}

Add yourself to the lxd group, so you can run ''lxc'' without being root:
{{Cmd|adduser {user} lxd}}
Then logout and login again.

== LXD configuration ==
Before you launch LXD containers, you must configure LXD:
{{Cmd|sudo lxd init}}
Accept all the defaults. You can rerun this if you have no containers.
The ZFS storage method is recommended, because of its ability to create instant snapshots and copies of containers, but it requires additional configuration and it is not available everywhere (e.g. in a VPS host). dir will do just fine for a demo.

== Container creation ==

To install Alpine Linux 3.8 run:
{{Cmd|lxc launch images:alpine/3.8 a1}}

To install Alpine Linux edge version run:
{{Cmd|lxc launch images:alpine/edge a2}}

To enter a shell in the container:
{{Cmd|lxc exec a1 ash}}

== Networking ==
The container has outgoing access to the network, but no incoming public access, since it doesn't have a public ip. You can provide incoming access using several networking techniques:
* On a LAN, it suffices to add a route through the host LXD node
* Use an iptables configurator, such as shorewall
* For HTTP/HTTPS access, use an HTTP reverse proxy/load balancer, such as haproxy or pound, to redirect HTTP requests to various containers. You can run the HTTP reverse proxy in an Alpine container, once you redirect the ports that you want to it, (using iptables).

[[Category:Virtualization]]

Install Alpine on LXD

2018-11-21T14:38:18Z

Votsalo: /* Networking */ haproxy

== LXD ==

LXD is an easy to use daemon and client for managing LXC containers. It is included by default in Ubuntu 16.04 and later versions. It may become available in other distributions, such as debian. If you are not familiar at all with LXC or LXD, start directly with LXD. For detailed instructions on how to use it, lookup Stéphane Graber's blog post series on LXD.

With LXD you can start an Alpine Linux container in seconds, in practically any Ubuntu 16.04 (or later) system, including:
* A standalone system
* An Amazon EC2 instance
* An OpenStack KVM VPS

These instructions assume you are running on an amd64 (x86_64) platform.

== LXD configuration ==
Before you launch LXD containers, you must configure LXD:
{{Cmd|sudo lxd init}}
Accept all the defaults. You can rerun this if you have no containers.
The ZFS storage method is recommended, because of its ability to create instant snapshots and copies of containers, but it requires additional configuration and it is not available everywhere (e.g. in a VPS host). dir will do just fine for a demo.

== Container creation ==

To install Alpine Linux 3.8 run:
{{Cmd|lxc launch images:alpine/3.8 a1}}

To install Alpine Linux edge version run:
{{Cmd|lxc launch images:alpine/edge a2}}

To enter a shell in the container:
{{Cmd|lxc exec a1 ash}}

== Networking ==
The container has outgoing access to the network, but no incoming public access, since it doesn't have a public ip. You can provide incoming access using several networking techniques:
* On a LAN, it suffices to add a route through the host LXD node
* Use an iptables configurator, such as shorewall
* For HTTP/HTTPS access, use an HTTP reverse proxy/load balancer, such as haproxy or pound, to redirect HTTP requests to various containers. You can run the HTTP reverse proxy in an Alpine container, once you redirect the ports that you want to it, (using iptables).

[[Category:Virtualization]]

Install Alpine on LXD

2018-07-09T06:35:18Z

Votsalo: removed "Fixing the Container" section. It is no longer needed. Use alpine 3.8 in example.

== LXD ==

LXD is an easy to use daemon and client for managing LXC containers. It is included by default in Ubuntu 16.04 and later versions. It may become available in other distributions, such as debian. If you are not familiar at all with LXC or LXD, start directly with LXD. For detailed instructions on how to use it, lookup Stéphane Graber's blog post series on LXD.

With LXD you can start an Alpine Linux container in seconds, in practically any Ubuntu 16.04 (or later) system, including:
* A standalone system
* An Amazon EC2 instance
* An OpenStack KVM VPS

These instructions assume you are running on an amd64 (x86_64) platform.

== LXD configuration ==
Before you launch LXD containers, you must configure LXD:
{{Cmd|sudo lxd init}}
Accept all the defaults. You can rerun this if you have no containers.
The ZFS storage method is recommended, because of its ability to create instant snapshots and copies of containers, but it requires additional configuration and it is not available everywhere (e.g. in a VPS host). dir will do just fine for a demo.

== Container creation ==

To install Alpine Linux 3.8 run:
{{Cmd|lxc launch images:alpine/3.8 a1}}

To install Alpine Linux edge version run:
{{Cmd|lxc launch images:alpine/edge a2}}

To enter a shell in the container:
{{Cmd|lxc exec a1 ash}}

== Networking ==
The container has outgoing access to the network, but no incoming public access, since it doesn't have a public ip. You can provide incoming access using several networking techniques:
* On a LAN, it suffices to add a route through the host LXD node
* Use an iptables configurator, such as shorewall
* For HTTP/HTTPS access, use an HTTP reverse proxy/load balancer, such as pound, to redirect HTTP requests to various containers. You can run the HTTP reverse proxy in an Alpine container, once you redirect the ports that you want to it, (using iptables).

[[Category:Virtualization]]

Installation

2017-04-28T07:37:23Z

Votsalo: /* Advanced */

The following information will assist you with the installation of [http://alpinelinux.org/about Alpine Linux].
[[Image:hdd_mount.png|left|link=]]
<br />

== Installation Quick-Start in 3 Easy Steps ==
<div style="float:left; font-size:30px; font-weight:bold;">
1st
</div>
<div style="margin-left:65px; background-color:#EDF2F2; border-style:solid; border-color:#6F7C91; border-width:0px; border-left-width:5px; min-height:55px; padding:5px;">
[http://alpinelinux.org/downloads Download] the latest stable-release ISO.
</div>

<div style="float:left; font-size:30px; font-weight:bold;">
2nd
</div>
<div style="margin-left:65px; background-color:#E0E9E9; border-style:solid; border-color:#606A82; border-width:0px; border-left-width:5px; min-height:55px; padding:5px;">
If you have a CD drive from which you can boot, then [[Burning ISOs|burn the ISO onto a blank CD]] using your favorite CD burning software. Else [[Create a Bootable USB|create a bootable USB drive]].
</div>

<div style="float:left; font-size:30px; font-weight:bold;">
3rd
</div>
<div style="margin-left:65px; background-color:#9faecc; border-style:solid; border-color:#324065; border-width:0px; border-left-width:5px; min-height:55px; padding:5px;">
Boot from the CD or USB drive, login as root with no password, and voilà! Enjoy Alpine Linux!
</div>

{{Clear}}
One of the [[Installation#Post-Install|first commands you might want to use]] is <code>[[setup-alpine]]</code>.

== Installation Handbook ==
=== Basics ===
Alpine can be used in any of three modes:
<dl>
<dt>diskless mode
<dd>You'll boot from read-only medium such as the installation CD, a [[Create a Bootable USB|USB drive]], or a [[Create a Bootable Compact Flash|Compact Flash card]]. {{Tip| To prepare either a USB or Compact Flash card, you can use the <code>[[setup-bootable]]</code> script; see the pages linked above for details.}} When you use Alpine in this mode, you need to use [[Alpine local backup|Alpine Local Backup (lbu)]] to save your modifications between reboots. That requires some writable medium, usually removable. (If your boot medium is, for example, a USB drive, you can save modifications there; you don't need a separate partition or drive.) See also [[Local APK cache]].
{{Note| When the <code>[[setup-alpine]]</code> script asks for a disk, say "none". It will then prompt whether you'd like to preserve modifications on any writable medium.}}
<dt>data mode
<dd>As in diskless mode, your OS is run from a read-only medium. However, here a writable partition (usually on a hard disk) is used to store the data in {{Path|/var}}. That partition is accessed directly, rather than copied into a tmpfs; so this is better-suited to uses where large amounts of data need to be preserved between reboots. {{Note| The <code>[[setup-alpine]]</code> script handles installing Alpine in this mode, too, when you supply a writable partition instead of "none", and request mode "data".}} This mode may be used for mailspools, database and log servers, and so on.
<dt>sys mode
<dd>This is a [[Install to disk|traditional hard-disk install]] (see link for details).  Both the boot system and your modifications are written to the hard disk, in a standard Linux hierarchy. {{Note| The <code>[[setup-alpine]]</code> script handles installing Alpine in this mode, too, when you supply a writable partition instead of "none", and request mode "sys". By default, it will create three partions on your disk, for {{Path|/boot}}, {{Path|/}}, and {{Path|swap}}; however you can also [[Setting up disks manually|partition your disk manually]].
}} This mode may be used for desktops, development boxes, and virtual servers.

</dl>

=== Advanced ===
* [[Create UEFI boot USB]]
* [[Tutorials_and_Howtos#Storage|Setting up storage with RAID, LVM, LUKS encryption, iSCSI, or suchlike]]
* [[Setting up disks manually]]
* [[Partitioning and Bootmanagers]]
* [[Migrating data]]
* Details about [[Alpine setup scripts]]

* [[Installing Alpine on HDD dualbooting|Install to HDD with dual-boot]]
* [[Replacing non-Alpine Linux with Alpine remotely]]



* [[Bootstrapping Alpine Linux]]


* [[Installing Alpine Linux in a chroot]]
* [[Install Alpine on LXC]]
* [[Install Alpine on LXD|Install Alpine on Ubuntu with LXD]]
* Install Alpine on [[Install Alpine on VirtualBox|VirtualBox]], [[Install Alpine on VMware|VMware]], [[Install Alpine on coLinux|coLinux]], [[Qemu]], , [[Install Alpine on Amazon EC2|Amazon EC2]], or [[Install Alpine on Rackspace|RackSpace]]

* [[Xen Dom0]] ''(Setting up Alpine as a dom0 for Xen hypervisor)''
* [[Xen Dom0 on USB or SD]]
* [[Create Alpine Linux PV DomU]]
* [[Xen LiveCD]]

* [[Setting up a basic vserver]]
* [[Setting up the build environment on HDD]]
* [[Setting up a compile vserver]] for official or for [[Setting up a compile vserver for third party packages|third party]] packages


=== Post-Install ===



* [[Tutorials_and_Howtos#Networking|Setting up Networking]]
* [[Alpine Linux package management|Package Management (apk)]] ''(How to add/remove packages on your Alpine)''

* [[Alpine local backup|Alpine local backup (lbu)]] ''(Permanently store your modifications in case your box needs reboot)''
** [[Back Up a Flash Memory Installation|Back Up a Flash Memory ("diskless mode") Installation]]
** [[Manually editing a existing apkovl]]
* [[Alpine Linux Init System|Init System (OpenRC)]] ''(Configure a service to automatically boot at next reboot)''
** [[Multiple Instances of Services]]

* [[Alpine setup scripts#setup-xorg-base|Setting up Xorg]]

* [[Upgrading Alpine]]


* [[Setting up a ssh-server]] ''(Using ssh is a good way to administer your box remotely)''
* [[setup-acf]] ''(Configures ACF (webconfiguration) so you can manage your box through https)''
* [[Hosting services on Alpine]]''(Links to several mail/web/ssh server setup pages)''
* [[Changing passwords for ACF|Changing passwords]]


* [[Setting the timezone]] ''(Not needed for the default musl- or uClibc-based installs)''

=== Further Help and Information ===
* [[FAQ|FAQs]]
* [[Tutorials and Howtos]]
* [[Contribute|How to Contribute]]
* [[Developer Documentation]]

[[Category:Installation]]

Install Alpine on LXD

2017-04-28T06:45:32Z

Votsalo: Created page with "== LXD == LXD is an easy to use daemon and client for managing LXC containers. It is included by default in Ubuntu 16.04 and later versions. It may become available in othe..."

== LXD ==

LXD is an easy to use daemon and client for managing LXC containers. It is included by default in Ubuntu 16.04 and later versions. It may become available in other distributions, such as debian. If you are not familiar at all with LXC or LXD, start directly with LXD. For detailed instructions on how to use it, lookup Stéphane Graber's blog post series on LXD.

With LXD you can start an Alpine Linux container in seconds, in practically any Ubuntu 16.04 (or later) system, including:
* A standalone system
* An Amazon EC2 instance
* An OpenStack KVM VPS

These instructions assume you are running on an amd64 (x86_64) platform.

== LXD configuration ==
Before you launch LXD containers, you must configure LXD:
{{Cmd|sudo lxd init}}
Accept all the defaults. You can rerun this if you have no containers.
The ZFS storage method is recommended, because of its ability to create instant snapshots and copies of containers, but it requires additional configuration and it is not available everywhere (e.g. in a VPS host). dir will do just fine for a demo.

To change the networking configuration:
{{Cmd|sudo dpkg-reconfigure -p medium lxd}}

== Container creation ==

To install Alpine Linux edge version run:
{{Cmd|lxc launch images:alpine/edge a1}}

To install Alpine Linux 3.5 run:
{{Cmd|lxc launch images:alpine/3.5 a2}}

To enter a shell in the container:
{{Cmd|lxc exec a1 ash}}

== Fixing the container ==
Once you create the container, edit /etc/inittab and comment out all lines that start with "tty". Otherwise, the container will keep writing warnings on /var/log/messages. Here's a script to automate this:
<pre>
#!/bin/sh

sed -i 's/^tty/# tty/g' /etc/inittab

# clean messages
rm /var/log/messages
</pre>

Let's say this script is called fixgetty.sh. To copy it to the container, use the following:
{{Cmd|lxc file push fixgetty.sh a1/root/}}

After you fix /etc/inittab, reboot the container:
{{Cmd|reboot}}

== Networking ==
The container has outgoing access to the network, but no incoming public access, since it doesn't have a public ip. You can provide incoming access using several networking techniques:
* On a LAN, it suffices to add a route through the host LXD node
* Use an iptables configurator, such as shorewall
* For HTTP/HTTPS access, use an HTTP reverse proxy/load balancer, such as pound, to redirect HTTP requests to various containers. You can run the HTTP reverse proxy in an Alpine container, once you redirect the ports that you want to it, (using iptables).

[[Category:Virtualization]]