DC/OS is installed in your environment by using a dynamically generated configuration 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 elements 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. For fully functional clusters on any infrastructure including on-premise, public or private clouds, follow the Production installation instructions. The Production installation method was previously called Custom installation.
The Universal Installer is the recommended tool for provisioning, deploying, installing, and upgrading DC/OS on a subset of our supported platforms. A more detailed overview and instructions for the Universal Installer may be found here.
Access DC/OS Configuration File
For installing DC/OS Enterprise Edition contact your sales representative or email@example.com. You can access the DC/OS Enterprise configuration file from the support website using a login credential. Enterprise
Hardware and software requirements for DC/OS deployments…Read More
Deploying DC/OS in a production-ready environment…Read More
Configuring your DC/OS using advanced configuration methods…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
Removing DC/OS…Read More