The usage topics help you run programs and services on an existing DC/OS cluster.


The DC/OS web interface provides a rich graphical view of your DC/OS cluster. With the web interface you can view the current state of your entire cluster and DC/OS services. The web interface is installed as a part of your DC/OS installation.


    You can use the DC/OS command-line interface (CLI) to manage your cluster nodes, install DC/OS packages, inspect the cluster state, and administer the DC/OS service subcommands.

    Using Containerizers

    A containerizer is a Mesos agent component responsible for launching containers, within which you can run a service. Running services in containers offers a number of benefits, including the ability to isolate tasks from one another and control task resources programmatically.

    Package Repository

    DC/OS comes pre-configured with the Mesosphere Universe package repository as the provider of DC/OS packages, but other package repositories can also be added.

      Service Discovery

      DC/OS provides a number of tools out-of-the-box, ranging from basic network connectivity between containers to more advanced features, such as load balancing and service discovery. Here’s an overview of the options, with some general guidelines on what to use in which situations.

      Managing Services

      DC/OS uses Marathon to manage processes and services. Marathon is the “init system” for DC/OS. Marathon starts and monitors your applications and services, automatically healing failures.


      You can create scheduled jobs in DC/OS without installing a separate service. Create and administer jobs in the DC/OS web interface, the DC/OS CLI, or via an API.


      This is the DC/OS tutorials section, covering how to use DC/OS components as well as stateless and stateful DC/OS services. Typically, the services discussed here are available and installable from the Universe.


      DC/OS applications lose their state when they terminate and are relaunched. In some contexts, for instance, if your application uses MySQL, or if you are using a stateful service like Kafka or Cassandra, you’ll want your application to preserve its state. Use local persistent volumes or external volumes to enable tasks to be restarted without data loss. Learn how to configure your cluster to use persistent volumes.


      We’ve collected some questions we often encounter concerning the usage of DC/OS. Have got a new question you’d like to see? Use the Submit feedback button at the bottom of this page to suggest it or check out how you can contribute also the answer to it.