Earlier quoted context omitted.
> Google Reader It still hurts.
It was the day RSS died for me
I'm glad it happened, now I'm happier with Feedly than I was back then with Google Reader.
Cluster and app management services in Docker Cloud are shutting down on May 21
71–80 of 155 posts
Re: Cluster and app management services in Docker Cloud are shutting down on May 21
#72We 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…
Why did you pick Swarm for production? We followed Swarm from the beginning, but after a few releases at v0.4 it was clear not to ever use Swarm, and that it mostly was the Docker PR machine that made it sound nice, and not the actual features. Maybe it got better later on, but the first several Swarm announcements seemed really off-putting to me. We ended up on Mesos/Marathon, not that that has a bright future eithe…
When we started looking for a container orchestration system, we naturally used Google Trends (https://trends.google.com/trends/explore?date=today%205-y&q=...). Kubernetes reached their 1.0 release shortly before we were ready to start using the system and a lot of the features added since then eliminated so of our other problems (e.g. configmaps/secrets combined with the existing service discovery pretty much eliminated our plans to use Consul).
I've been taking a second look at Mesos recently and found that I didn't really grok it the first time I looked at it. In any case, I think your assessment is correct ("Just migrate to Kubernetes" - https://trends.google.com/trends/explore?date=today%205-y&q=...).
Re: Cluster and app management services in Docker Cloud are shutting down on May 21
#73Earlier 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…
> Instead, I have to update every single client. To combat this, every single image we use from hub.docker.com is "proxied" into our registry with a one-line Dockerfile: FROM image:version Building the "proxy" image and publishing it in our registry is entirely automated (using CI+Registry of a self-hosted Gitlab). Then we make everything point to our version in our registry. Should hub.docker.com go belly-up, then w…
Do you do it per project or as a separate project that houses all the proxy images? How do you version the proxy images? What namespace do you push them into? Is it easy enough to deal with that it doesn’t waste a lot of time?
I’ve been trying to insulate myself from docker too and the FROM proxy strategy seems to break the least stuff. Have you hit any pain points?
Re: Cluster and app management services in Docker Cloud are shutting down on May 21
#74We 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…
I had to make a decision for an orchestration tool a few weeks ago and I went with K8s. One of the main reasons was that even Docker advertises it on its website and with Docker for Mac. I expect Swarm support to be canceled in a not so distant future and I cannot rely on a tool with an unclear future. Which is a pity because I really liked Swarm for its simplicity. Side note: I am also concerned about Docker in gene…
I'm not sure who's going to beat Docker. Docker is central to most orchestration tools so as long as they make money someplace with their central services, they should be fine.
Re: Cluster and app management services in Docker Cloud are shutting down on May 21
#75Earlier quoted context omitted.
I could see github adding a tab to repos as for a container registry. That would destroy docker hub imo.
GitLab has an integrated container registry since 2016. https://about.gitlab.com/2016/05/23/gitlab-container-registr...
Their devops for autobuilding, testing, and deploying are really awesome as well. We run an internal GitLab host that handles all deployments for us through their CI/CD interface.
Re: Cluster and app management services in Docker Cloud are shutting down on May 21
#76Had 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)
Re: Cluster and app management services in Docker Cloud are shutting down on May 21
#77Earlier 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…
But here we are talking about Docker Hub closing, which is way easier to solve. This is the registry that is used as default (for all non-local images without a URL identifier, like "alpine:latest"). All you need is an option to set the default registry. Probably it's already there, didn't google.
Google it. It’s a fun topic.
Re: Cluster and app management services in Docker Cloud are shutting down on May 21
#78How long until redhat buys docker?
Re: Cluster and app management services in Docker Cloud are shutting down on May 21
#79Earlier quoted context omitted.
Is there a hosted rancher service? I played around with it a long while ago and really liked it, but felt like more moving parts (and particularly on MySQL, which wasn't in our stack) wasn't something I was too keen on. Having someone manage this for us could be worth paying for though.
Rancher, the container orchestration, is pretty much dead too, since it's K8s-based from (upcoming) 2.0 on, i.e. it's becoming a K8s distribution and has to compete with K8s itself, OpenShift and probably upcoming open-sourced edition of Tectonic. RancherOS might live on, even though there is a lot of doubt on why it should do so.
I think you mean "cattle", the container orchestration system in Rancher 1.x
Rancher (and Rancher OS) seem to be doing fine and getting updates constantly.
We're eyeing Rancher 2.x and the Kubernetes integration but it gives me confidence seeing Rancher 1.x getting updated while they are so focused in 2.x and K8s.
Re: Cluster and app management services in Docker Cloud are shutting down on May 21
#80Earlier quoted context omitted.
Genuine question - what makes you think that Kubernetes has won? Well, "won" in quotes. I am not a k8s fanboy or anything, I simply observe that all the major cloud providers are offering managed k8s services that have superseded their own proprietary container-type offerings. For better or worse that's where the momentum is. If you wanted to containerize your stack right now, k8s then pick one of the big 3, seems li…
I've noticed the same trend, and as a fan of Docker Swarm, along with this news, I'm not happy about it. Compared to Kubernetes, Swarm is a breeze to setup, deploy and manage. The manifest files are the same Docker Compose files we're used to, just expanded to cover the new stack concepts. It has support for remote storage mounting, advanced networking configuration, various interesting volume and network plugins[0],…
Do you know if there are any good tools for migrating your manifest/compose yaml files to k8s, especially using more recent features such as configs and secrets?