about:system
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
about:system [2016/06/14 18:57] nuxwin |
about:system [2017/04/14 18:18] nuxwin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======i-MSCP Requirements====== | + | ====== System requirements ====== |
| - | =====General===== | + | * Debian: https://github.com/i-MSCP/imscp/blob/1.4.x/docs/Debian/INSTALL.md#1-requirements |
| - | + | * Ubuntu: https://github.com/i-MSCP/imscp/blob/1.4.x/docs/Ubuntu/INSTALL.md#1-requirements | |
| - | * 1 GHz or faster 32 bits (x86) or 64 bits (x64) processor (recommended) | + | |
| - | * 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 reiserfs, you 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. | + | |
| - | + | ||
| - | =====Distribution===== | + | |
| - | + | ||
| - | * Debian >= Wheezy (Base system with standard packages installed) | + | |
| - | * Ubuntu >= Precise Pangolin (Base system with standard packages installed) | + | |
| - | + | ||
| - | =====Software Version===== | + | |
| - | + | ||
| - | * PHP >= 5.3.2 | + | |
| - | * Perl >= 5.14.2 | + | |
| - | + | ||
| - | =====Note for Proxmox/Docker/LXC users===== | + | |
| - | + | ||
| - | If you want install i-MSCP inside a LXC container, the following conditions must be met: | + | |
| - | + | ||
| - | - You must have the ''CAP_MKNOD'' capability inside the container. Thus, you must ensure that `mknod` is not in the list of dropped capabilities (needed for pbuilder). | + | |
| - | - 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. | + | |
| - | - 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. | + | |
| - | - 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. | + | |
| - | + | ||
| - | **See also:** | + | |
| - | + | ||
| - | - https://linuxcontainers.org/fr/lxc/manpages/man5/lxc.container.conf.5.html | + | |
| - | - https://help.ubuntu.com/lts/serverguide/lxc.html#lxc-apparmor | + | |
/var/www/virtual/i-mscp.net/wiki/htdocs/data/pages/about/system.txt · Last modified: 2017/08/22 17:16 by nuxwin
