The services on Docker Cloud that provide application, node, and swarm cluster management will be shutting down on May 21. Other Docker Cloud SaaS offerings, such as automated builds and registry storage services, will not be affected and will continue to be available.

We know that this change presents an inconvenience in terms of how you will manage your containerized applications. To minimize the impact on your business, we will continue to provide support for any applications currently deployed in Docker Cloud until May 21.

To help you successfully migrate your applications to an alternative platform, the following FAQs are available:

Migrating to Other Docker Products

Docker EE is an enterprise-ready container platform for hybrid and multi-cloud environments

Migrating to Cloud Partners

FAQs

Will I continue to be charged for my nodes after May 21st?

A final invoice for node hours accrued up to May 21 will be generated. You will no longer accrue charges for node hours after May 21. Please note, that while you will no longer incur node management charges from Docker Cloud, you may still incur charges from your cloud provider while the nodes are deployed.

What will happen to my private repositories on Docker Cloud?

Repositories will be unaffected by this change. Docker Cloud will remain the best place to manage your repositories, builds, and teams & organizations.

What will happen to automated builds on Docker Cloud?

Any builds using the Docker Cloud build service will be unaffected by this change. However, you will no longer have the ability to perform builds on your own infrastructure and logs will no longer auto-update.

Does this include Docker Cloud 'Bring your own nodes'?

Yes. Any server that has the Docker Cloud Agent installed will be affected.

Where should I move my applications?

You can migrate to Docker Community Edition (CE) or Docker Enterprise Edition (EE) for deployments on-premises or in the cloud. If you’re interested in a fully managed cloud solution, Docker recommends Azure Container Service and Google Kubernetes Engine.

Docker provide migration guides for all of the products listed above, which can be found in the Docker docs.

What happens if I do not migrate by May 21st?

If you do not migrate by May 21, your applications running on the Docker node cluster management service will cease to operate.

Swarms will continue to function; however, if you do not retrieve your SSH keys for the Swarms being managed by our swarm cluster management service, you will be unable to access your swarms using your Docker ID. For instructions on how to retrieve and access your Swarms with SSH keys, please refer to the Docker docs.

If I have questions how can I get help?

If you have any questions about migrating off of Docker Cloud, please refer to our migration guides. Additional questions may be directed to cloudmigration@docker.com.

Why are you shutting down this service?

While we are discontinuing our managed cluster management service, we will continue to invest in our other products that provide cluster management like Docker Community Edition (CE) and Docker Enterprise Edition (EE). With these products, you have the flexibility to deploy in the cloud or on premises.

Is Docker Cloud going away?

No. Docker Cloud is not going away and will remain the primary destination to manage private repositories, builds, teams & organizations.

What happens to my user account data?

Docker IDs will be unaffected by this change. Your Docker ID will continue to be your single account to access all of Docker’s products and services. All repositories, builds, tests, teams & organizations will be unaffected.

I’m having login issues for Docker Cloud (incorrect password/connection error/etc.).

Users with a Docker ID can obtain assistance with non-technical customer service issues using the form on http://success.docker.com/support.