Getting Started

• Install Marathon
• Setup Recommendations
• High Availability Mode

Using Marathon

• Application Basics
• Application Deployments
• Application Groups
• Authorization and Access Control
• Blue-Green Deployment
• Constraints
• Event Bus
• Health Checks
• Marathon Web Interface
• Networking
• Pods
• Recipes
• Provisioning Containers
• Stateful Applications Using Local Persistent Volumes
• Stateful Applications Using External Persistent Volumes
• Task Environment Variables
• Task Handling
• Task Handling Configuration
• Secret Configuration
• Unreachable Strategy

Administration

• Command Line Flags
• Backup and Restore
• Data Migration
• Framework Authentication
• High Availability
• Metrics
• Deprecated Metrics
• Readiness Checks
• Checks
• Service Discovery and Load Balancing
• SSL and Basic Authentication
• Using a Private Docker Registry
• Maintenance mode
• Compatibility with Mesos

Upgrading

• Upgrading to a new Version
• Migrating Apps to the 1.5 Networking API
• Migrating Tools to the 1.5 Networking API
• Versioning

Troubleshooting

• Stuck App or Pod Deployments
• No new instances are starting
• An App Requires a Specific Host Port
• Error Using HTTPS with local CA Certificate
• Error Reading Authentication Secret
• Slow Docker apps and deployments
• Exit Codes

Development

• Contributor Guidelines
• Current Marathon Development
• Extend Marathon with Plugins
• Run a Local Version of Marathon

API Reference

• REST API Reference

Docs for Previous Versions

• Version 1.9.x
• Version 1.8.x
• Version 1.7.x

Migrating Apps to the 1.5 Networking API

When you upgrade to Marathon 1.5, your apps will also be automatically modified to conform to the new networking API. However, support for deprecated networking API fields will be dropped completely in some future release according to Marathon’s official API deprecation policy MARATHON-7165.

Use the options below to finely tune automatic app migration:

• Set the MIGRATION_1_5_0_MARATHON_DEFAULT_NETWORK_NAME environment variable.
  • Older MESOS IP/CT app definitions were not required to declare an ipAddress/networkName; Marathon 1.5 requires a resolvable network name.
  • Migration automatically configures container networking mode for each migrated legacy MESOS IP/CT app.
  • At migration time, legacy MESOS IP/CT app definitions are configured to use the network name defined by the migration-specific environment variable above.
• Use the --default_network_name flag.
  • Migration only uses the network name defined by the --default_network_name flag if the MIGRATION_1_5_0_MARATHON_DEFAULT_NETWORK_NAME environment variable is unset.

Note: For older MESOS IP/CT apps that do not declare a networkName: if neither the environment variable nor the flag are set, app migration will fail.