Latest revision |
Your text |
Line 6: |
Line 6: |
| or directly from http://distfiles.gentoo.org/releases/x86/current-stage3/ | | or directly from http://distfiles.gentoo.org/releases/x86/current-stage3/ |
| | | |
− | ----
| + | == Create directory for the new container and unarchive stage3 == |
− | | |
− | == Or try to Download 64 bit stage3 ==
| |
− | | |
− | 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/ 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 without multilib support (only 64bit binary support for gentoo template containers!!)
| |
− | | |
− | | |
− | 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:
| |
− | <pre>ACCEPT_KEYWORDS="amd64" in /etc/make.conf</pre> there you can accept 64bit binary packages support for your containers.
| |
− | <pre>cat /proc/cpuinfo</pre> for 64 bits Intel\AMD CPU instructions set support.
| |
− | | |
− | | |
− | '''WARNING''': There is no warrantied that template should work, you can bugtack the errors. But I haven't confronted with problem.
| |
− | | |
− | == Create directories for the new container and unarchive stage3 == | |
| | | |
| <pre> | | <pre> |
− | mkdir /vz/root/1001
| |
| mkdir /vz/private/1001 | | mkdir /vz/private/1001 |
− | tar -xvjpf /root/stage3-i686-20111213.tar.bz2 -C /vz/private/1001 | + | tar -xjf /root/stage3-i686-20111213.tar.bz2 -C /vz/private/1001 |
| </pre> | | </pre> |
| | | |
Line 47: |
Line 25: |
| </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 == |
| | | |
Line 65: |
Line 36: |
| values are providing 2 GB soft limit with 2.5 GB hard limit: | | values are providing 2 GB soft limit with 2.5 GB hard limit: |
| | | |
− | DISKSPACE="2.4G:2.5G" | + | DISKSPACE="2G:2.5G" |
− | | |
− | If you use independed Gentoo portage tree for each container, is considered correct in the use of gentoo containers, don't forget to raise inodes number
| |
− | | |
− | 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.
| |
− | Otherwise you can't reinstall already installed packages if you bind the newer version of portage in gentoo containers.
| |
| | | |
| After that you copy that configuration file turning it into a sample configuration for later use: | | After that you copy that configuration file turning it into a sample configuration for later use: |
Line 155: |
Line 108: |
| </pre> | | </pre> |
| | | |
− | Gentoo 11.2 release have an option in '''rc.conf''' | + | Gentoo 11.2 release have an option in /vz/private/1001/etc/rc.conf |
| just uncoment rc_sys and type "openvz" and it disables init scripts | | just uncoment rc_sys and type "openvz" and it disables init scripts |
| <pre> | | <pre> |
− | nano /vz/private/1001/etc/rc.conf
| |
| rc_sys="openvz" | | rc_sys="openvz" |
| </pre> | | </pre> |
Line 186: |
Line 138: |
| </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. |