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

Getting Started

After you have installed DC/OS and set up the CLI on your local machine, familiarize yourself with the DC/OS UI Dashboard and DC/OS CLI.

You can then launch a production-grade, highly available, containerized NGINX web server with a single command from the DC/OS CLI. DC/OS keeps your web server running if it crashes, allows you to scale it via the user interface and update its config at runtime, and much more!

  1. Run this command to launch a containerized sample app on DC/OS.

    dcos marathon app add
  2. Go to the “Services” tab of the DC/OS Dashboard to see the NGINX web server up and running and ready to serve traffic!

Now try these additional tutorials based on your role.


If you have a DevOps role:

If you have a data engineering or data scientists role:

If you have a DC/OS administrator role:

Intermediate or Advanced

If you’ve been playing around with DC/OS for a bit and want a deeper dive, see these tutorials.

If you want to learn more about how DC/OS works:

If you have a DevOps role:

If you have a DC/OS administrator role:

If you are now a seasoned DC/OS user and want to adapt or extend DC/OS, you can learn how to contribute!


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.


    Important: DC/OS 1.8 introduces binary CLIs for Linux, Windows, and Mac. The install script is replaced with a simple binary CLI. The 1.8 CLI is compatible with DC/OS 1.6.1 forward. For more information, see the documentation.

    Service Management with Marathon

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

    Private Docker Registry

    You can use a number of (hosted) options to store and manage your Docker images, but you can also set up a private Docker registry yourself and run it within your DC/OS cluster. This private registry is based on the Docker registry image and stores images in a system using one of the available storage drivers.

      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 Universe services are Marathon applications that are packaged and available from the DC/OS Universe repository. Available DC/OS services include Mesos frameworks and other applications. DC/OS services are created by the DC/OS community and by Mesosphere.


        This is a collection of tutorials about using DC/OS. Learn how to run services and operate services in production.


        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 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.