}}

Deploying Services and Pods

Updated: April 18, 2017

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.

A native Marathon instance is installed as a part of DC/OS installation. After DC/OS has started, you can manage the native Marathon instance through the Services tab of the DC/OS web interface or from the DC/OS CLI with the dcos marathon command.

DC/OS services are Marathon applications that are deployed on DC/OS. DC/OS services are available from a package repository, such as the Mesosphere Universe, or you can create your own.

DC/OS Services

You can run DC/OS services you create or install a package from the Universe package repository. Both services you create and those you install from Universe appear on the Services tab of the DC/OS web interface when they are running.

Services you create yourself are administered by Marathon and can be configured and run from the DC/OS CLI with dcos marathon subcommands (e.g. dcos marathon app add <myapp>.json) or via the DC/OS web interface.

Universe Package Repository

Packaged DC/OS services created by Mesosphere or the community, like Spark or Kafka, appear on the Universe tab of the DC/OS web interface, or you can search for a package from the DC/OS CLI. You can configure and run Universe services from the DC/OS web interface or via the DC/OS CLI with the dcos package install <package-name> command. Visit the Managing Services section to learn more about installing, configuring, and uninstalling services in Universe.

Installing Services

Installing a service using the CLI The general syntax for installing a service with the CLI follows. dcos package install [--options=<config-file-name>.json] <servicename&...

Configuring Universe Services

Each Universe service installs with a set of default parameters. You can discover the default parameters and change them as desired. This topic describes how to use the DC/OS CLI t...

Monitoring Services

You can monitor deployed DC/OS services from the CLI and web interface. Monitoring Universe services CLI From the DC/OS CLI, enter the dcos service command. In this example you can...

Service Ports

Port configuration for applications in Marathon can be confusing and there is an outstanding issue to redesign the ports API. This page attempts to explain more clearly how they wo...

Updating a User-Created Service

You can easily view and update the configuration of a deployed app by using the dcos marathon command. Note: The process for updating packages from the DC/OS Universe is different....

Using a Private Docker Registry

To supply credentials to pull from a private Docker registry, create an archive of your Docker credentials, then add it as a URI in your application definition. Step 1: Compress Do...

Exposing a Service

DC/OS agent nodes can be designated as public or private during installation. Public agent nodes provide access from outside of the cluster via infrastructure networking to your DC...

Uninstalling Services

Services can be uninstalled from either the web interface or the CLI. If a Universe service has any reserved resources, you also need to run the framework cleaner script. The frame...

Using Mesos Containerizers

Containerizers allow you to run tasks in containers. Running tasks in containers offers a number of benefits, including the ability to isolate tasks from one another and control ta...

Marathon REST API

The Marathon API allows you to manage long-running containerized services (apps and pods). The Marathon API is backed by the Marathon component, which runs on the master nodes. One...

Frequently Asked Questions

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