Install Alpine on LXD - Revision history

Abrahms: copy + pastable group change

2020-11-14T20:43:34Z

copy + pastable group change

← Older revision		Revision as of 20:43, 14 November 2020
Line 23:		Line 23:

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

Votsalo at 09:26, 18 January 2019

2019-01-18T09:26:28Z

← Older revision		Revision as of 09:26, 18 January 2019
Line 1:		Line 1:
	== LXD ==		== 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~~.		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:		With LXD you can start an Alpine Linux container in seconds, in practically any Ubuntu 16.04 (or later) system, including:
Line 7:		Line 7:
	* An Amazon EC2 instance		* An Amazon EC2 instance
	* An OpenStack KVM VPS		* 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.		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 ==		== LXD configuration ==

Votsalo: /* Networking */ haproxy

2018-11-21T14:38:18Z

Networking: haproxy

← Older revision		Revision as of 14:38, 21 November 2018
Line 31:		Line 31:
	* On a LAN, it suffices to add a route through the host LXD node		* On a LAN, it suffices to add a route through the host LXD node
	* Use an iptables configurator, such as shorewall		* 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).		* 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]]		[[Category:Virtualization]]

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

2018-07-09T06:35:18Z

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

@@ Line 17: / Line 17: @@
 == Container creation ==
 To install Alpine Linux edge version run:
-{{Cmd|lxc launch images:alpine/edge a1}}
+{{Cmd|lxc launch images:alpine/edge a2}}
 To enter a shell in the container:
 {{Cmd|lxc exec a1 ash}}
 == Networking ==

Fcolista: Seems that the user copy/pasted the doc from a debian-oriented distro documentation...

2017-05-17T06:52:23Z

Seems that the user copy/pasted the doc from a debian-oriented distro documentation...

← Older revision		Revision as of 06:52, 17 May 2017
Line 15:		Line 15:
	Accept all the defaults. You can rerun this if you have no containers.		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.		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 ==		== Container creation ==

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..."

2017-04-28T06:45:32Z

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..."

New page

== 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]]