User Tools

Site Tools


about:system

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
about:system [2016/06/14 18:57]
nuxwin
about:system [2017/08/22 17:16] (current)
nuxwin
Line 1: Line 1:
-======i-MSCP Requirements======+====== ​System requirements ​======
  
-=====General=====+  * 1 GHz or faster 32 bits (x86) or 64 bits (x64) processor 
 +  * 1 Gio memory (minimum) - For heavily loaded servers or high flow is recommended at least 8 Gio 
 +  * 1 Gio of available hard disk space for i-MSCP and managed services, excluding user data 
 +  * Internet access (at least 100 Mbits/s recommended) 
 +  * A Linux kernel >2.6.26 
 +  * A file system supporting extended attributes such as ext2, ext3, ext4 or reiserfs***** 
 +  * Appropriate privileges to create devices (**CAP_MKNOD** capability) 
 +  * Appropriate privileges to mount, unmount and remount filesystems (**CAP_SYS_ADMIN** capability)
  
-  * 1 GHz or faster 32 bits (x86) or 64 bits (x64) processor (recommended) +===== Reiserfs users =====
-  * 1 Gio memory (minimum) - For heavily loaded servers or high flow is recommended at least 16 Gio +
-- 2 Gio of available hard disk space for i-MSCP and managed services, excluding user data +
-  * Internet access (100 Mbits/s recommended) +
-  * A file system that supports extended attributes such as ext2, ext3, ext4 or reiserfs*.+
  
-In case of reiserfsyou must ensure that your file system is mounted with the **attrs** option. See [[start:​howto:​reiserfs|Using ​reiserfs file system with i-MSCP]] for more information.+In orderto use the reiserfs file system with i-MSCP, you must follow these steps:
  
-=====Distribution=====+Edit your **/​etc/​fstab** file to add the **attrs** option for your device (e.g. device containing the /var partition). For 
 +instance: 
 +    UUID=74699091-3ab8-43f2-bdd5-d1d898ab50fd /     ​reiserfs notail ​         0    1 
 +should be updated to: 
 +    UUID=74699091-3ab8-43f2-bdd5-d1d898ab50fd /     ​reiserfs notail,​attrs ​   0    1 
 +Once you did that, you can remount your device. For instance: 
 +    mount -o remount /​dev/​disk/​by-uuid/​74699091-3ab8-43f2-bdd5-d1d898ab50fd 
 +If needed, you can find the uuid of your device, with the following command: 
 +    blkid <​device>​ 
 +where **<​device>​** must be replaced by your device path such as **/​dev/​sda1**
  
-  * Debian >Wheezy (Base system with standard packages installed) +===== LXC containers =====
-  * Ubuntu >Precise Pangolin (Base system with standard packages installed)+
  
-=====Software Version=====+If you want install i-MSCP inside a LXC container, the following conditions have to be met:
  
-  * PHP >= 5.3.2 +  * You must have the **CAP_MKNOD** capability inside the containerThus, you must ensure that **mknod** is not in the list of dropped capabilities 
-  * Perl >5.14.2+  * You must have the **CAP_SYS_ADMIN** capability inside the container (required to mount filesystems). Thus, you must ensure that `sys_admin` is not in the list of dropped capabilities
 +  * You must allow the creation of devices inside the container by white-listing them. Easy solution is to add **lxc.cgroup.devices.allow ​a *:* rwm** in LXC container configuration file. 
 +  * If you use **Apparmor**,​ you must allow **mount**,​**umount** and **remount** operations inside your container by modifying the default apparmor profile **/​etc/​apparmor.d/​lxc/​lxc-default** or by creating a specific apparmor profile for the container.
  
-=====Note for Proxmox/​Docker/​LXC users=====+Note that these operations must be done on the host, not in the container.
  
-If you want install i-MSCP inside a LXC container, the following conditions must be met: +**See also:** 
-  +  ​* https://i-mscp.net/index.php/​Thread/​14039-i-MSCP-inside-a-LXC-container-Managed-by-Proxmox-4-x 
-  - You must have the ''​CAP_MKNOD''​ capability inside the containerThus, you must ensure that `mknod` is not in the list of dropped capabilities (needed for pbuilder). +  * https://​linuxcontainers.org/​fr/​lxc/​manpages/​man5/​lxc.container.conf.5.html 
-  ​You must have the ''​CAP_SYS_ADMIN''​ capability inside the container (needed for mount(8)). Thus, you must ensure that `sys_admin` is not in the list of dropped capabilities. +  ​* https://help.ubuntu.com/lts/​serverguide/lxc.html#lxc-apparmor 
-  ​You must allow the creation of devices ​inside ​the container by white-listing them (needed for pbuilder)Easy solution is to add ''​lxc.cgroup.devices.allow = a *:* rwm''​ in LXC container configuration file+  * http://​wiki.apparmor.net/​index.php/​AppArmor_Core_Policy_Reference#​Mount_rules_.28AppArmor_2.8_and_later.29
-  ​- If you use ''​Apparmor'',​ you must allow bindmounts inside your container by modifying the default apparmor profile ''​/etc/apparmor.d/lxc/lxc-default''​ or by creating a specific ​apparmor ​profile for the container.+
  
-Note that all those operations must be done on the host, not in the container.+===== OpenVZ containers (Proxmox and Virtuozzo) =====
  
-**See also:**+You could have to increase the **fs.ve-mount-nr** limit, else, an error such as **mountCannot allocate memory** could be threw by CageFS. To avoid this problem you must: 
 + 
 +  - Increase the limit by adding an entry such as **fs.ve-mount-nr = 4096** to your **/​etc/​sysctl.conf** file 
 +  - Make the new limit effective by executing the **sysctl -p** command
  
-  - https://​linuxcontainers.org/​fr/​lxc/​manpages/​man5/​lxc.container.conf.5.html +Note that these operations must be done on the host, not in the container.
-  - https://​help.ubuntu.com/​lts/​serverguide/​lxc.html#​lxc-apparmor+
/var/www/virtual/i-mscp.net/wiki/htdocs/data/attic/about/system.1465930652.txt.gz · Last modified: 2016/06/14 18:57 by nuxwin