Cluster and app management services in Docker Cloud are shutting down on May 21

We are extremely worried about the future of Docker Swarm as well. We love Swarm - but we are seeing most work out of the Docker team is to give a migration path to kubernetes. A huge number of docker swarm networking bugs are not being worked on.<p>We will be happy if Docker talks about Swarm becoming a management UX for K8s - but we need visibility. These are production orchestration systems. The migration path is not easy.<p>And seeing what Docker Co is doing with Cloud, it is not very comforting to trust that they will do the right thing with Swarm.

People, yours truly included, seem a bit concerned with the 2 months notice.<p>To be fair docker cloud was never great and hopefully it doesn&#x27;t have many big customers...<p>But the precedence of shutting down a paid service with 2 months notice is not nice. What would happen if this was docker hub? Panic!

Twitter users are up in arms because of the decision to retire production systems with a 2 months notice - <a href="https:&#x2F;&#x2F;twitter.com&#x2F;thomashermine&#x2F;status&#x2F;976398123215065088" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;thomashermine&#x2F;status&#x2F;976398123215065088</a><p><a href="https:&#x2F;&#x2F;twitter.com&#x2F;garethdiz&#x2F;status&#x2F;976188140670017536" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;garethdiz&#x2F;status&#x2F;976188140670017536</a><p><a href="https:&#x2F;&#x2F;twitter.com&#x2F;LenioLabsLLC&#x2F;status&#x2F;976201790482915328" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;LenioLabsLLC&#x2F;status&#x2F;976201790482915328</a>

Please keep docker swarm going guys, it&#x27;s a great product.<p>Docker cloud is no loss (with apologies to those who are using it in production) and will hopefully free up your people to work on other important stuff.<p>Otherwise if we can continue to use the compose configuration api and the docker deploy&#x2F;service api with k8s under the hood then I guess that&#x27;s a reasonable compromise.

Had a startup in this area, with swarm under the hood, and realised last year (when RackSpace closed Carina) that 1. swarm is loosing momentum due to the ammount of new features, stability and native cloud integration that k8s brought; 2. containers are beeig adopted at a huge speed, and big cloud providers like aws and gce have lots of users and trust, so the effort of offer CaaS is not that big, with great chances of success; 3. The hosting market is tough due to comprtition. DigitalOcean was in this market way before they were caled DO.; 4. When you want to make money from OSS like Docker does, companies like RedHat and IBM allready have years ahead of competition due to their established sales channels (in 1-2y from now we will see tectonic in all rhel powered companies, and docker announcing that it’s not supporting UCP any more)

The timing of this (shutdown on 21 May) made me wonder if it&#x27;s related to the GDPR coming into effect starting on 25 May.

Given the time it takes to migrate the production stack to another system (one or more months), this won&#x27;t be enough time for many users to migrate. There is no drop-in replacement. It is pretty abrupt of them to give a 60 day notice.<p>On a meta thought, I wonder what potentially caused this move. It is&#x2F;was a pretty decent service.

I was logged into docker the other day and saw this notification but I didn’t—and still don’t—know exactly what services they’re referring to. Do they mean everything under cloud.docker.com, the swarms beta, or something else?

It was long known since they did not ship any new update since August 2016. We at Turing Analytics migrated to Rancher labs about 6 months ago.<p>They should have announced it earlier and should have given more time to paying customers. I am glad I migrated very early.

Wasn&#x27;t the whole point of docker containers that deploys and migrations are a breeze?

As I read through this all it feels sort of weird even typing it but I kind of hope Amazon or Microsoft buys Docker rather than Oracle, Google or IBM.<p>I think Microsoft still employs thousands of great engineers and have been early embracers of containerization among the large companies out there and because Satya was a large part of growing Azure into what it is (IMHO a pretty solid set of services) it could make a lot of sense

This is why your company or product should not depend on that new cool SaaS&#x2F;PaaS.

Damn. My last company ran a bunch of production things in Docker Cloud. Contrary to many opinions, I kinda liked it. It was cheap and fairly simple to use. The API was straightforward and way less expansive and cumbersome than something like AWS ECS.

What was the point of acquiring Tutum killing it, rebranding to Docker Cloud and killing it as well.<p>Tutum actually worked and I really liked it. Now I plan to use Rancher on top of kubernetes for my docker hosting

Long time docker user here.<p>Docker Cloud was getting worse and worse. Tutum (they acquired, rebranded and killed it) was great. But docker team just destroyed it.<p>That is a shame. Tutum was great since it scaled up and <i></i>down<i></i> very well. Nobody thinks about scaling down, but this is important in many ways.<p>Right now IMO: - Docker swarm - scales up and down ok. Had too many bugs with even on stable. - Rancher - fine, very good for medium deployments. - k8 - winner for larger scale but scales down badly.<p>This is really sad.

Please keep swarm mode going. It’s a pleasure to use, easy to set up, works well with Compose and overall satisfies a lot use cases. Thanks for your work!

I&#x27;ve been meaning to learn kubernetes for a while now having been a docker compose user for a few years. Swarm seemed super appealing due to easy migration and simplicity. Having gone through a few tutorials for Kube I still feel a little overwhelmed with the volume of configuration, and also how local development is meant to be done. This was always a very cool part of compose.

Docker really needs to provide some transparency around these decisions. People are concerned about the future of the ecosystem. They have every right to shutdown aspects of their offering. But the community deserves an explainstion. This notice didn’t even attempt to explain the decision. Is Docker stopping development on swarm? Getting out of the PaaS business? Downsizing?

Wow this is very surprising.<p>I&#x27;ve been working on a Docker Cloud alternative for awhile now. I&#x27;m aiming for something that kind of balances the convenience of Heroku with the Docker experience.<p>It&#x27;s still in beta but if anyone wants to check it out it&#x27;s at: <a href="https:&#x2F;&#x2F;codemason.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;codemason.io&#x2F;</a>

What exactly is docker cloud and how does it fit in the docker workflow?

How long until redhat buys docker?

GDPR killed Docker Cloud. It&#x27;s not the last victim we will see.

Docker the file format&#x2F;command line syntax&#x2F;etc will long outlive Docker the company<p>Kubernetes “won” so now the competition has shifted from who can innovate to who can execute and operate.

I always chuckle when people put so much trust in &quot;startup&quot; companies. It&#x27;s the same like believing in IBM not trying to screw you over.<p>There&#x27;s a reason why people and businesses hate vendor lock ins. There&#x27;s a reason why we do not want AWS to reign supreme for long.