Live data from Hacker News

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

docs.docker.com

141–150 of 155 posts

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

#141
post #100

Earlier quoted context omitted.

i would encourage you to try Swarm. Its brilliant in its simplicity. I think Docker product marketing and customer success basically sucks. But Swarm as a product has been really, really nice. And yes I continuously evaluate kubernetes and swarm side by side. You can get a swarm cluster running in less than 10 minutes on your local laptop after "apt-get install docker-ce". To run k8s, you will need to first muck abou…

$ brew cask install minikube $ minikube start

What about HA / clustering, security mTLS?

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

#143
post #5

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

It's a managed application service where you bring your own node, from the cloud or from on-prem. It gives you a dashboard & end to end management of applications running on your nodes.

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

#144

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?

How is the community affected in any way by this decision? Docker cloud is a management product and only open to paying customers.

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

#145
post #99

Earlier quoted context omitted.

I’m concerned as well. We use Docker and Docker Compose heavily for our development and both on Docker for Windows and Docker for Mac developers have to restart their daemon several times a day. The binaries aren’t open so it’s tough to see and fix the issue; but because we aren’t Docker Enterprise Engine customers, there is no path to support. It would be helpful if there were a way to pay for Docker and receive sup…

Yikes. Surely Docker is providing you more than $200 worth of value a month. If so, why would you only pay $200?

I might; but that’d have to mean seeing some traction from that money first. They haven’t proven that they’re able to run the sort of business they’re trying to run.

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

#148

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

Could it be that the teams are simply focused on adding K8s support and getting the Docker EE out of Beta?

Public statement on their blog after the K8s announcement in EU:

"But it’s equally important for us to note that Swarm orchestration is not going away. Swarm forms an integral cluster management component of the Docker EE platform; in addition, Swarm will operate side-by-side with Kubernetes in a Docker EE cluster, allowing customers to select, based on their needs, the most suitable orchestration tool at application deployment time."

https://blog.docker.com/2017/11/swarm-orchestration-in-docke...

There's still plenty of PR's and activity in the SwarmKit and Libnetwork repos:

https://github.com/docker/swarmkit/pulse/monthly https://github.com/docker/libnetwork/pulse/monthly

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

#149
post #33

Earlier quoted context omitted.

docker hub is surprisingly difficult to replace because of how docker registries work. Traditional package managers have two distinct concepts: a repository and packages within those repositories. For example, if ubuntu took down their apt repo server, I could run my own with all the same packages and change a single sources.list entry and all my servers, ansible roles installing packages, etc, would operate the same…

Does it actually send the URL? I think it uses the URL to make the network request, but doesn’t actually send the URL to the registry. If it did, you could use an alternate registry as a pull through cache and have it go upstream for everything. AFAIK that’s not possible.

Docker's registry protocol is surprisingly complicated. It is stateful, it is not trivially cacheable, and it's a right pain in the ass to deal with

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

#150
post #117
post #109

Earlier quoted context omitted.

Is HashiCorp’s Nomad in a similar position at this point? I really enjoy it’s (relative) simplicity.

I get the impression that Nomad was never particularly alive to begin with, which is a shame since it seems better designed. But it doesn't have that "ZOMG Google has blessed us with the secrets of the borg" that DevOps crave.

I, too, was sad to see similar things with Nomad. HashiCorp really does write generally excellent software.
Post reply on HN