Installation - Revision history

Fog: /* RHEL */

2025-02-07T00:28:39Z

‎RHEL

Fog: /* CentOS */

2025-02-07T00:27:49Z

‎CentOS

SebastianRoth: /* LXC */

2021-05-19T12:23:29Z

‎LXC

SebastianRoth: /* VirtualBox */

2020-02-22T09:49:31Z

‎VirtualBox

SebastianRoth: /* Command line options */

2020-02-22T09:46:14Z

‎Command line options

SebastianRoth: /* Ubuntu */

2020-02-22T09:39:11Z

‎Ubuntu

SebastianRoth: /* Ubuntu */

2020-02-22T09:37:47Z

‎Ubuntu

SebastianRoth: /* Requirements */

2020-02-22T09:34:29Z

‎Requirements

SebastianRoth: /* OpenVZ */

2018-10-25T08:50:48Z

‎OpenVZ

Wayne-workman.28155: Updated documentation.

2018-03-16T22:45:52Z

Updated documentation.

@@ Line 108: / Line 108: @@
 === RHEL ===
 TBA
 === Ubuntu ===

@@ Line 91: / Line 91: @@
 [[Installation on CentOS 6.4|CentOS 6.4]] (CentOS 6.5 also works),
 [[Installation on CentOS 5.3|CentOS 5.3]] (CentOS 5.4 & 5.5 also covered)
 === Debian ===

@@ Line 194: / Line 194: @@
 === LXC ===
-LXC (used in Proxmox for example) does need some manual configuration tweek - [https://forums.fogproject.org/topic/7978/fog-in-lxc-container-how-to-configure-nfs-server reference]:
+One of the main things is to get NFS to work within LXC containers. While it used to be easy in Proxmox newer versions make it more complicated.
-profile lxc-container-default-cgns flags=(attach_disconnected,mediate_deleted) {
+Proxmox 6.x: https://forums.fogproject.org/topic/15176/fog-server-in-lxc-container-under-proxmox-6
-  # the container may never be allowed to mount devpts.  If it does, it
+Proxmox 5.x: An update (around 23th of October 2018) broke NFS in LXC containers. Find a fix here: https://forum.proxmox.com/threads/mounting-nfs-in-lxc-not-working-since-latest-update.47815/
-* Reload Apparmor: <pre>apparmor_parser -r /etc/apparmor.d/lxc-containers</pre>
+Proxmox 4.x: https://forums.fogproject.org/topic/7978/fog-in-lxc-container-how-to-configure-nfs-server
 === VirtualBox ===

@@ Line 222: / Line 222: @@
 === VirtualBox ===
-Bridged network, host only. Older versions have (PXE?) bug - Tom knows about that.
+Bridged network or host only.
-Have we seen this issue in the FOG forums yet? http://forum.ipxe.org/showthread.php?tid=7864
+Most versions seem to suffer from a bug where iPXE would only be able to get an IP from the DHCP if started cold (vs. reboot).
 === VMWare ESXi ===

@@ Line 43: / Line 43: @@
   ./installfog.sh --help
- ...
+  Usage: ./installfog.sh [-h?dEUuHSCKYXTFA] [-f <filename>] [-N <databasename>]
-  * Found FOG Settings from previous install at: /opt/fog/.fogsettings
+  		[-D </directory/to/document/root/>] [-c <ssl-path>]
   		[-W <webroot/to/fog/after/docroot/>] [-B </backup/path/>]
   		[-s <192.168.1.10>] [-e <192.168.1.254>] [-b <undionly.kpxe>]
   	-h -? --help			Display this info
   	-d    --no-defaults		Don't guess defaults
   	-U    --no-upgrade		Don't attempt to upgrade
   	-H    --no-htmldoc		No htmldoc, means no PDFs
-  	-S    --force-https		Force HTTPS redirect
+  	-S    --force-https		Force HTTPS for all comunication
   	-C    --recreate-CA		Recreate the CA Keys
   	-K    --recreate-keys		Recreate the SSL Keys
   	-Y -y --autoaccept		Auto accept defaults and install
   	-f    --file			Use different update file
-  	-c    --ssl-file		Specify the ssl path
+  	-c    --ssl-path		Specify the ssl path
   	               				defaults to /opt/fog/snapins/ssl
   	-D    --docroot			Specify the Apache Docroot for fog
@@ Line 80: / Line 73: @@
   	-X    --exitFail		Do not exit if item fails
   	-T    --no-tftpbuild		Do not rebuild the tftpd config file
-  	-P    --no-pxedefault		Do not overwrite pxe default file
+  	-F    --no-vhost		Do not overwrite vhost file
+ 	-A    --arm-support		Install kernel and initrd for ARM platforms
 === .fogsettings ===

@@ Line 121: / Line 121: @@
 === Ubuntu ===
 [[Ubuntu 16.04]]
-[[Ubuntu 14.04]],
+(<font color="red">obsolete, just for the archive:</font> [[Ubuntu 14.04]],
 [[Ubuntu 12.04|Ubuntu 13.10]],
 [[Ubuntu 12.04|Ubuntu 13.04]],
@@ Line 132: / Line 132: @@
 Ubuntu 8.10,
 Ubuntu 8.04,
-[[Installation on 7.10|Ubuntu 7.10]]
+[[Installation on 7.10|Ubuntu 7.10]])
 == Virtualization ==

@@ Line 2: / Line 2: @@
 Before diving right into the installation of FOG you need to decide which server OS you are going to use. FOG is made to install on RedHat based distro CentOS, Fedora, RHEL amongst others as well as Debian, Ubuntu and Arch Linux. Choose whichever you like most and have knowledge about! FOG is known to work with any of the above noted systems. Many [[Installation#Installation_manuals|installation manuals]] are available.
-This listing is for informational purposes only, as the required components will be automatically downloaded and installed by the FOG installation script: PHP 5/6/7, MySql 5+, Apache 2+, DHCP (any!), TFTP, FTP, NFS
+This listing is for informational purposes only, as the required components will be automatically downloaded and installed by the FOG installation script: PHP 5/7, MySql 5+/MariaDB 10+, Apache 2+, DHCP (pretty much any!), TFTP, FTP, NFS
 The LAMP setup can also be easily adjusted for a "WAMP (Windows Apache MySQL PHP) system" though will require a bit more knowledge of what packages to use and how to integrate with the FOG system.
@@ Line 8: / Line 8: @@
 Please choose the distribution you have the most knowledge about, but the below list has the best support in FOG 1.3.0 right now. This list is by no means an absolute list to follow, though.
-*  Ubuntu 14 or higher
+* Ubuntu 16 or higher
 * Debian 8 or higher
 * Red Hat 6 or higher

← Older revision		Revision as of 08:50, 25 October 2018
Line 199:		Line 199:

	To be able to send WOL and multicast packages the container needs a proper MAC address. This is only the case if you configure the container to use a network bridge (veth instead of venet!).		To be able to send WOL and multicast packages the container needs a proper MAC address. This is only the case if you configure the container to use a network bridge (veth instead of venet!).
		+
		+	=== LXC ===
		+	LXC (used in Proxmox for example) does need some manual configuration tweek - [https://forums.fogproject.org/topic/7978/fog-in-lxc-container-how-to-configure-nfs-server reference]:
		+	* Option 1 - Disable Apparmor:
		+	** Edit the container configuration file and add the line lxc.aa_profile: unconfined.
		+	** On Proxmox the configuration file is located at /etc/pve/lxc/CTID.conf, where CTID is the ID number of the container.
		+	* Option 2 - Edit Apparmor profile to allows NFS:
		+	** Open /etc/apparmor.d/lxc/lxc-default-cgns and add the nfs/rpc lines:
		+	<pre>
		+	# Do not load this file. Rather, load /etc/apparmor.d/lxc-containers, which
		+	# will source all profiles under /etc/apparmor.d/lxc
		+
		+	profile lxc-container-default-cgns flags=(attach_disconnected,mediate_deleted) {
		+	#include <abstractions/lxc/container-base>
		+
		+	# the container may never be allowed to mount devpts. If it does, it
		+	# will remount the host's devpts. We could allow it to do it with
		+	# the newinstance option (but, right now, we don't).
		+	deny mount fstype=devpts,
		+	mount fstype=cgroup -> /sys/fs/cgroup/**,
		+	mount fstype=nfs*,
		+	mount fstype=rpc_pipefs,
		+	}
		+	</pre>
		+
		+	* Reload Apparmor: <pre>apparmor_parser -r /etc/apparmor.d/lxc-containers</pre>
		+
		+	'''Important:''' The latest Proxmox update (around 23th of October 2018) broke NFS in LXC containers. Find a fix here: https://forum.proxmox.com/threads/mounting-nfs-in-lxc-not-working-since-latest-update.47815/

	=== VirtualBox ===		=== VirtualBox ===

@@ Line 19: / Line 19: @@
 == Download FOG ==
+Please see: [[Getting_FOG]]
 == Installer ==