Replicated and Docker Swarm

A quick overview of how to get started with the Replicated Docker Swarm scheduler.

This content is associated with a legacy version of the Replicated product. For the current Replicated product documentation, see

Replicated can be used with a Docker Swarm application to deploy an enterprise-installable version of your application. Replicated provides developers with the ability to support their applications, allow users to configure it for their enterprise environment, and offer their application as an appliance. When using Docker Swarm with Replicated, developers continue to get all of the functionality of the Replicated platform while having access to all of the Docker Swarm functionality.

When to Use the Docker Swarm Scheduler

Compared to other schedulers supported by Replicated, Docker Swarm offers:

  • Single daemon provisioining and scaling, while offering multiple node distribution and overlay networking.
  • Docker Compose release format, allowing developers to more closely mirror Replicated releases to development and SaaS environments
  • Built-in overlay networking and DNS-based service discovery
  • Cluster-wide service load balancing

Distribute a Swarm Application

The process to distribute your Swarm application in Replicated consists of the following steps:

  1. Create a new team on the Replicated Vendor Portal.
  2. Prepare the images required by your app. You can either:
    • Tag and push your images to the Replicated Private Registry. Or
    • Select images from a public registry ie Docker Hub. Or
    • Push your images to a third party private registry & provide Replicated with access.
  3. Define your components on the Replicated Vendor Portal.
  4. Create a release of your application.
  5. Install your application to test.

The next section describes the release YAML format for Docker Swarm in more detail.