DC/OS Enterprise is designed to be configured, deployed, managed, scaled, and upgraded on any cluster of physical or virtual machines. You can install DC/OS in the environment of your choice by using a customized setup file or cloud templates.
Custom Setup File
The DC/OS Enterprise setup file is generated by using specific parameters that are set in your configuration file. 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 DC/OS setup file can be deployed using these methods:
The 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. A shared SSH key is required for this method.
The 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. A shared SSH key is required for this method.
The advanced installer provides a scriptable, automatable interface to integrate with your preferred configuration management system. 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.
DC/OS offers configurable cloud provisioning templates for AWS that manage a DC/OS installation on virtual machines. The DC/OS templates for AWS CloudFormation bring power and flexibility to creating and extending DC/OS clusters. For more information, see the documentation.
The local installer deploys DC/OS with Vagrant. This method is designed for first-time users or developers looking to build services or modify DC/OS. The Vagrant installer provides a quick, free way to deploy a virtual cluster on a single machine.
DC/OS Custom Installation Options
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.…Read More
DC/OS Cloud Installation Options
You can install DC/OS on AWS by using cloud templates.…Read More
The local installation method uses Vagrant to create a cluster of virtual machines on your local machine that can be used for demos, development, and testing with DC/OS.…Read More
A DC/OS patch describes a set of changes and supporting data designed to update, fix, or improve the features/functionality of DC/OS. A point release that consists of minor changes is also called a patch.…Read More
An upgrade is the process of adding new features, replacing the existing features with new features/functionality or adding a major configuration change. You can upgrade DC/OS only if you have used the installation process to install DC/OS on your cluster. Example: 1.X to 1.Y (1.10 --> 1.11)…Read More
DC/OS components listen on multiple ports on each node. These ports must be available for installation to succeed.…Read More
You can opt-out of the provided authentication by disabling it for your cluster. To disable authentication, add this parameter to your config.yaml file during installation (note this requires using the CLI or advanced installers):…Read More
Frequently Asked Questions
We recommend starting with a fresh cluster to ensure all defaults are set to expected values. This prevents unexpected conditions related to mismatched versions and configurations.…Read More
Troubleshooting a DC/OS Enterprise installation…Read More