Gentoo template creation - Revision history

Dasa at 15:23, 12 March 2016

2016-03-12T15:23:39Z

Dasa: /* Set up udev */

2013-02-25T00:36:19Z

‎Set up udev

Dasa: /* Edit CT Config */

2013-02-25T00:22:38Z

‎Edit CT Config

Dasa: /* Create directories for the new container and unarchive stage3 */

2013-02-25T00:06:03Z

‎Create directories for the new container and unarchive stage3

91.190.93.145: /* Edit CT Config */

2013-02-06T10:26:42Z

‎Edit CT Config

72.84.91.66: /* Create directory for the new container and unarchive stage3 */

2012-11-14T02:38:13Z

‎Create directory for the new container and unarchive stage3

24.229.230.100: whith -> with

2012-06-29T13:02:19Z

whith -> with

24.229.230.100: Minor spelling/grammar fixes

2012-06-29T13:01:01Z

Minor spelling/grammar fixes

91.190.93.145: /* Disable unneeded init scripts */

2012-06-01T09:10:40Z

‎Disable unneeded init scripts

91.190.93.145 at 10:33, 30 May 2012

2012-05-30T10:33:31Z

← Older revision		Revision as of 15:23, 12 March 2016
Line 47:		Line 47:
	</pre>		</pre>

		+	If you get the following error, you need to change the file /etc/vz/vz.conf to "VE_LAYOUT=simfs". Unfortunately, I couldn't find a solution for ploop.
		+	<pre>
		+	# vzctl set 1001 --applyconfig basic --save
		+	Error in ploop_open_dd (di.c:288): Can't resolve /vz/private/1001/root.hdd/DiskDescriptor.xml: No such file or directory
		+	Failed to read /vz/private/1001/root.hdd/DiskDescriptor.xml
		+	Error: failed to apply some parameters, not saving configuration file!
		+	</pre>
	== Edit CT Config ==		== Edit CT Config ==

← Older revision		Revision as of 00:36, 25 February 2013
Line 179:		Line 179:
	</pre>		</pre>

		+	'''Baselayout 2 and OpenRC:''' <code>/vz/private/1001/etc/conf.d/rc</code> is obsolete (http://www.gentoo.org/doc/en/openrc-migration.xml#doc_chap2_sect2) and <code>/vz/private/1001/etc/rc.conf</code> should be used instead. But, RC_DEVICES is missing in <code>/vz/private/1001/etc/rc.conf</code>?!?

	If you want to enable udev read on.		If you want to enable udev read on.

← Older revision		Revision as of 00:22, 25 February 2013
Line 63:		Line 63:

	DISKINODES="400000:420000"		DISKINODES="400000:420000"
		+
		+	You should also increase the ram to a minimum of 512 MB. Otherwise, you will get errors during compilation. Since vzctl 3.0.30 you can do:
		+
		+	vzctl set 1001 --ram 512M --swap 1G --save
		+
		+	Prior to vzctl 3.0.30 you have to do, which gives you 512 MB guaranteed and 1024 MB burstable:
		+
		+	vzctl set 1001 --vmguarpages 512M --save
		+	vzctl set 1001 --oomguarpages 512M --save
		+	vzctl set 1001 --privvmpages 512M:1024M --save
		+	vzctl set 1001 --swappages 0:1024M --save

	Independed Gentoo portage tree for each container would be good idea, because newer portage can delete older ebuilds already installed in container with other dependences.		Independed Gentoo portage tree for each container would be good idea, because newer portage can delete older ebuilds already installed in container with other dependences.

@@ Line 32: / Line 32: @@
 mkdir /vz/root/1001
 mkdir /vz/private/1001
-tar -xjf /root/stage3-i686-20111213.tar.bz2 -C /vz/private/1001
+tar -xvjpf /root/stage3-i686-20111213.tar.bz2 -C /vz/private/1001
 </pre>

@@ Line 58: / Line 58: @@
 values are providing 2 GB soft limit with 2.5 GB hard limit:
-  DISKSPACE="2G:2.5G"
+  DISKSPACE="2.4G:2.5G"
 After that you copy that configuration file turning it into a sample configuration for later use:

@@ Line 27: / Line 27: @@
 '''WARNING''': There is no warrantied that template should work, you can bugtack the errors. But I haven't confronted with problem.
-== Create directory for the new container and unarchive stage3 ==
+== Create directories for the new container and unarchive stage3 ==
 <pre>
 mkdir /vz/private/1001
 tar -xjf /root/stage3-i686-20111213.tar.bz2 -C /vz/private/1001

@@ Line 10: / Line 10: @@
 == Or try to Download 64 bit stage3 ==
-If you experience with 32bit containers you can also try to create Gentoo template whith 64bits binary support. Try to download '''64bit''' stage3. For 64bit Gentoo template creation, search for nearest mirrors http://www.gentoo.org/main/en/mirrors.xml or directly from:
+If you experience with 32bit containers you can also try to create Gentoo template with 64bits binary support. Try to download '''64bit''' stage3. For 64bit Gentoo template creation, search for nearest mirrors http://www.gentoo.org/main/en/mirrors.xml or directly from:
-http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3/ whith 32bit binary '''multilib''' support, or
+http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3/ with 32bit binary '''multilib''' support, or
-http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3/hardened/ (stage3-amd64-hardened+nomultilib-20xxxxxx.tar.bz2) try the hardend profile whithout multilib support (only 64bit binary support for gentoo template containers!!)
+http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3/hardened/ (stage3-amd64-hardened+nomultilib-20xxxxxx.tar.bz2) try the hardend profile without multilib support (only 64bit binary support for gentoo template containers!!)
@@ Line 25: / Line 25: @@
-'''WARNING''': There is no warrantied that template should work, you can bugtack the errors. But I haven't confronted whith problem.
+'''WARNING''': There is no warrantied that template should work, you can bugtack the errors. But I haven't confronted with problem.
 == Create directory for the new container and unarchive stage3 ==

@@ Line 10: / Line 10: @@
 == Or try to Download 64 bit stage3 ==
-If you experience whith 32bit containers you can also try to create Gentoo template whith 64bits binary support. Try to download '''64bit''' stage3. For 64bit Gentoo template creation, search for nearest mirrors http://www.gentoo.org/main/en/mirrors.xml or directly from:
+If you experience with 32bit containers you can also try to create Gentoo template whith 64bits binary support. Try to download '''64bit''' stage3. For 64bit Gentoo template creation, search for nearest mirrors http://www.gentoo.org/main/en/mirrors.xml or directly from:
 http://distfiles.gentoo.org/releases/amd64/autobuilds/current-stage3/ whith 32bit binary '''multilib''' support, or
@@ Line 18: / Line 18: @@
-Don't forget that hostnode must support 64bit binary too whith or whithout 32bit multilib support!! Hostnodes that supports multilib can start 64bits containers whith 32bits containers but has some '''''little''''' downtirn whith perfomance.
+Don't forget that hostnode must support 64bit binary too, with or without 32bit multilib support!! Hostnodes that supports multilib can start 64bits containers with 32bits containers but with a '''''slight''''' performance degradation.
 Don't forget to look for:

@@ Line 129: / Line 129: @@
 </pre>
-Gentoo 11.2 release have an option in /vz/private/1001/etc/rc.conf
+Gentoo 11.2 release have an option in '''rc.conf'''
 just uncoment rc_sys and type "openvz" and it disables init scripts
 <pre>
 rc_sys="openvz"
 </pre>

@@ Line 5: / Line 5: @@
 We will make the template from a stage3 file. An OpenVZ OS template should be an archive (.tar.gz) of the root of a working system, but without the kernel and some files. You can download stage3 from the nearest mirror from http://www.gentoo.org/main/en/mirrors.xml
 or directly from http://distfiles.gentoo.org/releases/x86/current-stage3/
 == Create directory for the new container and unarchive stage3 ==