DC/OS is installed in your environment by using a dynamically generated setup file. This file is generated by using specific parameters that are set during configuration. This installation file contains a Bash install script and a Docker container that is loaded with everything you need to deploy a customized DC/OS build. The Docker container contains all of the bits for DC/OS so it can be used for offline installation.
The DC/OS installation process requires a cluster of nodes to install DC/OS onto and a single node to run the DC/OS installation from.
You must have a single bootstrap node, Mesos master nodes, and Mesos agent nodes.…Read More
The automated GUI installer provides a simple graphical interface that guides you through the installation of DC/OS. The GUI 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.…Read More
The automated CLI installer provides a guided installation of DC/OS from the command line. With this method you can choose from the complete set of DC/OS configuration options.…Read More
With this installation method, you package the DC/OS distribution yourself and connect to every node manually to run the DC/OS installation commands. This installation method is recommended if you want to integrate with an existing system or if you don’t have SSH access to your cluster.…Read More
To remove DC/OS, you must completely reimage the operating system on your nodes. Uninstall will be supported in future releases. For more information, see DCOS-250 and DCOS-192.…Read More
You can opt-out of providing anonymous data by disabling telemetry for your cluster. To disable telemetry, add this parameter to your config.yaml file during installation (note this requires using the CLI or advanced installers):…Read More
The DC/OS configuration parameters are specified in YAML format in a config.yaml file. This file is stored on your bootstrap node and is used during DC/OS installation to generate a customized DC/OS build.…Read More
Configure DC/OS for Proxy
By default the DC/OS Universe repository is hosted on the internet. If your DC/OS cluster is behind a corporate proxy, you must specify your proxy configuration in the configuration file file before installation. This will enable your cluster to connect to the Universe packages.…Read More
Node and Cluster Health Checks
Node and cluster health checks provide information about your cluster, including available ports, Mesos agent status, and IP detect script validation. A health check is a shell command that reports the status of a DC/OS cluster or node via its exit code. You can write your own custom health checks or use the predefined checks.…Read More