PLDWWW: Vserver

[patrys]

Author: patrys   Date: Sun Jan  8 12:31:15 2006 GMT
Module: PLDWWW   URL: http://pld-linux.org/Vserver
---- Log message:


---- Page affected: Vserver

---- Diffs:

================================================================
   * [http://www.gentoo.org/doc/en/vserver-howto.xml Gentoo Linux-VServer Howto] you'll need this if you want to setup Gentoo guest vserver
   * [http://linux-vserver.org/index.php?page=Linux-VServer-Paper-08 Field of Application paper] reasons why to use vserver.
  
+ 
+ ---- /!\ '''Edit conflict - other version:''' ----
  == Installing host PLD Linux Vserver ==
  
  Build and install kernel
  {{{
  ./builder -r kernel-2_6_12_6-0_1 --with vserver --without grsecurity kernel.spec
  poldek -u kernel-vserver
+ 
+ ---- /!\ '''Edit conflict - your version:''' ----
+ == Installing Vserver host on PLD Linux ==
+ 
+ Build and install the kernel:
+ {{{
+ $ ./builder -r kernel-2_6_12_6-0_1 \
+ --with vserver --without grsecurity kernel.spec
+ 
+ ---- /!\ '''End of edit conflict''' ----
+ 
+ ---- /!\ '''Edit conflict - other version:''' ----
  }}}
  
  If you also run desktop on that host you might want to:
  {{{
  poldek -u kernel-vserver-sound-{alsa,oss}
+ 
+ ---- /!\ '''Edit conflict - your version:''' ----
+  poldek -u kernel-vserver
+ }}}
+ 
+ If you also run a desktop on that host you might want to:
+ {{{
+ # poldek -u kernel-vserver-sound-{alsa,oss}
+ 
+ ---- /!\ '''End of edit conflict''' ----
  }}}
  
  == Installing guest PLD Linux Vserver ==
  
+ 
+ ---- /!\ '''Edit conflict - other version:''' ----
  === preparing userspace tools ===
  {{{
  poldek -u util-vserver{,-build,-init}
@@ -70, +96 @@

  
  == configuring network ==
  
+ ---- /!\ '''Edit conflict - your version:''' ----
+ === Preparing userspace tools ===
+ 
+ First, install the tools:
+ {{{
+ # poldek -u util-vserver{,-build,-init}
+ }}}
+ 
+ Then configure ''poldek.conf'':
+ {{{
+ # vim /etc/vservers/.distributions/pld2.0/poldek/poldek.conf
+ }}}
+ 
+ At this point you should have booted into vserver-enabled kernel.
+ You must start {{{vprocunhide}}} or none of your Vservers can start.
+ 
+ To start {{{vprocunhide}}}:
+ {{{
+ # /etc/rc.d/init.d/vprocunhide start
+ }}}
+ 
+ === Actual guest creation ===
+ 
+ Build the guest system:
+ {{{
+ # vserver /etc/vservers/test build -m poldek -n test
+ }}}
+ 
+ Install {{{rc-scripts}}} to the new system using {{{vpoldek}}}:
+ {{{
+ # vpoldek test -- -u rc-scripts
+ }}}
+ 
+ And then start the guest system:
+ {{{
+ # vserver test start
+ }}}
+ 
+ To enter that vserver, type:
+ {{{
+ # vserver test enter
+ }}}
+ 
+ Note, however, that if you don't run ''plain'' init style you must have at least one daemon running inside your guest vserver or it will be shut down shortly.
+ 
+ == Configuring the network ==
+ 
+ ---- /!\ '''End of edit conflict''' ----
+ 
  {{{/etc/vservers/<vserver-name>/interfaces/<iface>}}}
  
  'iface' is an arbitrary name for the interface; the value itself is not important but may be interesting regarding interface-creation and usage with chbind. Both happens in alphabetical order and numbers like '00' are good names for these directories. 
@@ -84, +159 @@

   * {{{prefix}}} The network prefix-length.
   * {{{scope}}} The scope of the network interface.
  
- == managing packages ==
+ == Managing packages ==
  
+ You can manage your packges using {{{vpoldek}}}:
+ 
- Syntax: vpoldek VSERVER -- REGULAR POLDEK OPTIONS
+ Syntax: {{{vpoldek <VSERVER> -- [REGULAR POLDEK OPTIONS]}}}
+ 
- for example:
+ For example:
  {{{
- vpoldek test -- -u squid
+ # vpoldek test -- -u squid
  }}}
  
+ You can also use {{{vrpm}}}:
+ 
- Syntax: vrpm VSERVER -- REGULAR RPM OPTIONS
+ Syntax: {{{vrpm <VSERVER> -- [REGULAR RPM OPTIONS]}}}
+ 
- for example:
+ For example:
  {{{
- vrpm test -- -qa 'apache-*'
+ # vrpm test -- -qa 'apache-*'
  }}}
  
- you should always manage your packages outside vserver. it provides extra security and avoids duplicating rpm database and installed libraries/packages. if you have no good reason for otherwise, keep it outside.
+ You should always manage your packages from the outside of your vserver. It provides extra security and avoids duplicating RPM database and installed libraries/packages. If you have no good reason for doing otherwise, keep it outside.
  
- to convert rpmdb to inside there's doc: 
+ To convert {{{rpmdb}}} from outside of the guest to inside, see this doc: 
  {{{
  less /usr/share/doc/util-vserver-build-0.30.209/package-menagament.txt.gz
  }}}
  
- == using init style plain ==
+ == Using plain init style ==
  
- you might want to run your vserver with init style plain, which means it runs like regular linux host, where everything is controlled by {{{/sbin/init}}}. other reasons for doing so is that you can't enter your vserver because it dies before you can enter it :)
+ You might want to run your vserver with init style set to ''plain'', which means it runs like a regular Linux host, where everything is controlled by {{{/sbin/init}}}. The other reason for doing so is that it might happen that you can't enter your vserver because it gets shut down before you can enter it because of no running processes.
+ 
+ To enable ''plain'' init style:
  
  {{{
- echo 'plain' > /etc/vservers/test/apps/init/style
+ # echo 'plain' > /etc/vservers/test/apps/init/style
  }}}