Ubuntu 14.04 and LXC containers - Revision history

Necros at 08:02, 1 March 2015

2015-03-01T08:02:25Z

Necros at 08:00, 1 March 2015

2015-03-01T08:00:37Z

Necros: /* LXC container creation */

2015-02-28T19:04:20Z

‎LXC container creation

Necros: /* LXC container creation */

2015-02-28T18:58:51Z

‎LXC container creation

Necros: /* LXC container creation */

2015-02-28T18:57:40Z

‎LXC container creation

Necros: /* LXC container creation */

2015-02-28T18:52:11Z

‎LXC container creation

Necros at 18:47, 28 February 2015

2015-02-28T18:47:08Z

Necros at 15:18, 28 February 2015

2015-02-28T15:18:55Z

Necros at 22:20, 27 February 2015

2015-02-27T22:20:09Z

Necros at 21:16, 27 February 2015

2015-02-27T21:16:51Z

← Older revision		Revision as of 08:02, 1 March 2015
Line 1:		Line 1:
	Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run in these containers.		Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run in these containers.
		+
		+	Here's how to setup a FOG server in a LXC container.

	= Prerequisites =		= Prerequisites =

@@ Line 9: / Line 9: @@
 Setup a bridge on the computer, with at least one ethernet interface attached to it.
-apt-get install bridgeutils
+apt-get install bridge-utils
 edit the file '''/etc/network/interfaces''' and add the following lines. '''Please ensure you're not using a SSH session''', because you may lose your connection !

@@ Line 43: / Line 43: @@
    lxc-start -n server-fog -F
-login with the login and password given earlier, and '''change the password''' ! If needed, you have to shutdown the container to go back to the host's console
+login with the credentials given earlier, and '''change the password''' ! If needed, you have to shutdown the container to go back to the host's console
    sudo init 0

← Older revision		Revision as of 18:58, 28 February 2015
Line 84:		Line 84:
	* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.		* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.
	* chmod 777 /images		* chmod 777 /images
		+
		+	Once your setup is up and running, do not forget to enable autostart of your container :
		+
		+	edit /var/lib/lxc/server-fog/config :
		+
		+	lxc.start.auto = 1

@@ Line 43: / Line 43: @@
    lxc-start -n server-fog -F
-login with the login and password given earlier, and '''change the password''' ! you have to shutdown the container to go back to the host's console
+login with the login and password given earlier, and '''change the password''' ! If needed, you have to shutdown the container to go back to the host's console
    sudo init 0
-check the connectivity
+To run the container non interactively, use the following command
-You have to download, compile and install unfs3 from sources.
+  lxc-start -d -n server-fog
 * [http://sourceforge.net/projects/unfs3/files/ Download unfs3]

@@ Line 29: / Line 29: @@
 First, create a LXC container running Ubuntu. The version is the latest LTS version available at the moment of creating the container
-lxc-create -n server-fog -t ubuntu -B lvm --vgname vg --lvname lv-server-fog --fssize=10G --fstype=ext4
+  lxc-create -n server-fog -t ubuntu -B lvm --vgname vg --lvname lv-server-fog --fssize=10G --fstype=ext4
-This will create a logical volume '''lv-server-fog''' in the volume group '''vg0''', with a 10GB ext4 filesystem. The container wil be named '''server-fog'''.
+This will create a logical volume '''lv-server-fog''' in the volume group '''vg0''', with a 10GB ext4 filesystem. The container wil be named '''server-fog'''. At the end of the process, the system will give you a login and a password.
-Edit the file '''/var/lib/lxc/server-fog/config''' to assign a static IP address to
+Edit the file '''/var/lib/lxc/server-fog/config''' and setup networking for the container :
 You have to download, compile and install unfs3 from sources.

← Older revision		Revision as of 18:47, 28 February 2015
Line 1:		Line 1:
−	Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run ~~under~~ these containers.	+	Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run in these containers.
		+
		+	= Prerequisites =
		+
		+	* A computer (physical or virtual) running Ubuntu 14.04 Server, may or may not using LVM, with available space in at least one volume group
		+
		+	= Network setup on the LXC host =
		+
		+	Setup a bridge on the computer, with at least one ethernet interface attached to it.
		+
		+	apt-get install bridgeutils
		+
		+	edit the file '''/etc/network/interfaces''' and add the following lines. '''Please ensure you're not using a SSH session''', because you may lose your connection !
		+
		+	Add the following lines :
		+	auto br0
		+	iface br0 inet static
		+	address 192.168.1.2
		+	netmask 255.255.255.0
		+	gateway 192.168.1.1
		+	bridge_ports eth0
		+	bridge_fd 0
		+	bridge_maxwait 0
		+
		+	Reboot the computer and check network connectivity
		+
		+	= LXC container creation =
		+
		+	First, create a LXC container running Ubuntu. The version is the latest LTS version available at the moment of creating the container
		+
		+	lxc-create -n server-fog -t ubuntu -B lvm --vgname vg --lvname lv-server-fog --fssize=10G --fstype=ext4
		+
		+	This will create a logical volume '''lv-server-fog''' in the volume group '''vg0''', with a 10GB ext4 filesystem. The container wil be named '''server-fog'''.
		+
		+	Edit the file '''/var/lib/lxc/server-fog/config''' to assign a static IP address to

	You have to download, compile and install unfs3 from sources.		You have to download, compile and install unfs3 from sources.

← Older revision		Revision as of 15:18, 28 February 2015
Line 1:		Line 1:
−	Ubuntu releases after 10.04 LTS do no longer provide unfs3 to ~~workaround~~ OpenVZ ~~and~~ LXC containers ~~limitations~~	+	Ubuntu releases after 10.04 LTS do no longer provide unfs3. Unfs3 is useful when one want to setup a fog server in a container with OpenVZ or LXC. Nfs kernel server cannot run under these containers.

	You have to download, compile and install unfs3 from sources.		You have to download, compile and install unfs3 from sources.

← Older revision		Revision as of 22:20, 27 February 2015
Line 25:		Line 25:
	* restart the container, and check the nex volume is available : run mount without any argument.		* restart the container, and check the nex volume is available : run mount without any argument.
	* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.		* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.
		+	* chmod 777 /images

@@ Line 20: / Line 20: @@
 If you want to setup a separate volume for your images :
-assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :
+* assuming you want to use a logical volume (LVM) /dev/vg0/lv with a ext3 filesystem :
+* run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck
-run your container and move all files located in /images into an other location (/root/images-bak), including the hidden file /images/.mntcheck
+* from the lxc host, open /var/lib/your-container/fstab and add the following line : /dev/vg0/lv images ext3 defaults 0 0
+* restart the container, and check the nex volume is available : run mount without any argument.
-from the lxc host, open /var/lib/your-container/fstab and add the following line
+* If the LVM volume has been successfully mounted, move back the files backed up in /root/images-bak. Note there is no slash before '''images'''.