The automated GUI installer provides a simple graphical interface that guides you through the installation of DC/OS. The automated installer provides a basic installation that is suitable for demonstrations and POCs. Only a subset of the configuration options are available with the GUI method. This is the fastest way to get started with DC/OS.
This installation method uses a bootstrap node to administer the DC/OS installation across your cluster. The bootstrap node uses an SSH key to connect to each node in your cluster to automate the DC/OS installation.
Important: Upgrades are not supported with this installation method.
The DC/OS installation creates these folders:
||Contains all the DC/OS binaries, libraries, cluster configuration. Do not modify.|
||Contains the systemd services which start the things that make up systemd. They must live outside of
||Contains copies of the units in
||Contains the ZooKeeper data.|
||Contains the Docker data.|
||Contains the DC/OS data.|
||Contains the Mesos data.|
Important: Changes to
/opt/mesosphere are unsupported. They can lead to unpredictable behavior in DC/OS and prevent upgrades.
Download the DC/OS installer to your bootstrap node.
curl -O https://downloads.dcos.io/dcos/stable/dcos_generate_config.sh
From your terminal, start the DC/OS GUI installer with this command.
sudo bash dcos_generate_config.sh --web
Here is an example of the output.
Running mesosphere/dcos-genconf docker with BUILD_DIR set to /home/centos/genconf 16:36:09 dcos_installer.action_lib.prettyprint:: ====> Starting DC/OS installer in web mode 16:36:09 root:: Starting server ('0.0.0.0', 9000)
Tip: You can add the verbose (
-v) flag to see the debug output:
sudo bash dcos_generate_config.sh --web -v
Launch the DC/OS web installer in your browser at:
Click Begin Installation.
Specify your Deployment and DC/OS Environment settings:
Master Private IP List
Specify a comma-separated list of your internal static master IP addresses.
Agent Private IP List
Specify a comma-separated list of your internal static private agent private IP addresses.
Agent Public IP List
Specify a comma-separated list of your internal static public agent private IP addresses.
Master Public IP
Specify a publicly accessible proxy IP address to one of your master nodes. If you don’t have a proxy or already have access to the network where you are deploying this cluster, you can use one of the master IP’s that you specified in the master list. This proxy IP address is used to access the DC/OS web interface on the master node after DC/OS is installed.
Specify the SSH username, for example
SSH Listening Port
Specify the port to SSH to, for example
Private SSH Key
Specify the private SSH key with access to your master IPs.
DC/OS Environment Settings
Upstream DNS Servers
Specify a comma-separated list of DNS resolvers for your DC/OS cluster nodes. Set this parameter to the most authoritative nameservers that you have. If you want to resolve internal hostnames, set it to a nameserver that can resolve them. If you have no internal hostnames to resolve, you can set this to a public nameserver like Google or AWS. In the example above, the Google Public DNS IP addresses (IPv4) are specified:
220.127.116.11. If Google DNS is not available in your country, you can replace the Google DNS servers with your local DNS servers.
Caution: If you set this parameter incorrectly you will have to reinstall DC/OS. For more information about service discovery, see the documentation.
IP Detect Script
Choose an IP detect script from the dropdown to broadcast the IP address of each node across the cluster. Each node in a DC/OS cluster has a unique IP address that is used to communicate between nodes in the cluster. The IP detect script prints the unique IPv4 address of a node to STDOUT each time DC/OS is started on the node. For more information about IP detect scripts, see the advanced install documentation.
Important: The IP address of a node must not change after DC/OS is installed on the node. For example, the IP address must not change when a node is rebooted or if the DHCP lease is renewed. If the IP address of a node does change, the node must be wiped and reinstalled.
Send Anonymous Telemetry
Indicate whether to allow Mesosphere to collect anonymous DC/OS usage data. For more information, see the documentation.
Indicate whether to enable authentication for your DC/OS cluster. For more information, see the documentation.
Click Run Pre-Flight. The preflight script installs the cluster prerequisites and validates that your cluster is installable. For a list of cluster prerequisites, see the scripted installer prerequisites. This step can take up to 15 minutes to complete. If errors any errors are found, fix and then click Retry.
*Important: If you exit your GUI installation before launching DC/OS, you must do this before reinstalling:
* SSH to each node in your cluster and run `rm -rf /opt/mesosphere`. * SSH to your bootstrap master node and run `rm -rf /var/lib/dcos/exhibitor/zookeeper` ![preflight](/1.10/img/dcos-gui-run-preflight.png)
Click Deploy to install DC/OS on your cluster. If errors any errors are found, fix and then click Retry.
Tip: This step might take a few minutes, depending on the size of your cluster.
Click Run Post-Flight. If errors any errors are found, fix and then click Retry.
- If you encounter errors such as
Time is marked as bad,
Time not in syncduring Post-Flight, verify that Network Time Protocol (NTP) is enabled on all nodes. For more information, see the system requirements.
- You can click Download Logs to view your logs locally.
- If this takes longer than about 10 minutes, you’ve probably misconfigured your cluster. Go checkout the troubleshooting documentation.
- If you encounter errors such as
Click Log In To DC/OS. If this doesn’t work, take a look at the troubleshooting docs.
You are done!
It is recommended that you save your DC/OS installer file immediately after installation completes and before you start using DC/OS. These installer files can be used to add more agent nodes to your cluster, including the public agent node.
From your bootstrap node, navigate to the
genconf/servedirectory and package the contents as
# <Ctrl-C> to exit installer cd genconf/serve sudo tar cf dcos-install.tar *
dcos-install.tarfile to another location for backup. For example, you can use Secure Copy (scp) to copy
dcos-install.tarto your home directory:
exit scp -i $username@$node-ip:~/genconf/serve/dcos-install.tar ~