Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lessons learned from using Docker Swarm mode in production

blog.bugsnag.com

Post reply on HN
Print view View original

51–55 of 55 posts

Re: Lessons learned from using Docker Swarm mode in production

#51

Post by noselasd »

2sk21 wrote: post #49
derefr wrote: post #44

Earlier quoted context omitted.

Consider that they have different target audiences. Docker itself is mostly targeted as a tool for developers : you, the developer, dockerize your application, resulting in a container-image. Sure, that container-image then has to get deployed by someone (who isn't necessarily you), but the reason it's getting deployed at all is that a developer, at some point, made a decision to use Docker as part of the development…

I have been wondering - whats the business model for Docker itself?

Selling training, support and docker datacenter (http://www.docker.com/products/docker-datacenter)

Re: Lessons learned from using Docker Swarm mode in production

#52

Post by noselasd »

colemickens wrote: post #42
rb808 wrote: post #16

While we're on the topic can anyone recommend a system for rolling out (Java) applications across server farms that doesn't use containers? We have a bunch of shell scripts that are pretty horrible. We could containerize, but we dont need that right now.

I don't get it. Containerizing your apps will help with many things including reliable rollouts. It's trivial to containerize a Java app. Do you just not want to learn about containers? Using a container orchestrator for deployment is pretty much better than using a CM tool in every way... and it's certainly better than trying to half-ass one with bash scripts.

It is not always trivial to get buy in from your manager to shift your entire datacenter to running docker, or db admins, or the other dev teams, nor might it be trivial to tell the ops guys to go figure out how to run it.

If you are all of the above yourself - tings are much easier

Re: Lessons learned from using Docker Swarm mode in production

#53

Post by ovi256 »

madmax96 wrote: post #30
jahewson wrote: post #24

Honestly, you should try kubernetes. The experience is pretty much the same and the feature set is much more mature.

My experience with Kubernetes is limited, so take all this with a grain of salt. I've been using the integrated swarm since beta. The new integrated swarm is a real game-changer in that it is much simpler to use compared to other solutions. With swarm, it's simply: docker swarm init docker swarm join --token That being said, I found that Kubernetes offers more granularity in the level of control over the cluster. Tha…

I've had the same great, simple experience with Flynn. The terminal commands you give are barely different from Flynn's. And I like Flynn's capabilities better, at least for now. They've already figured out the routing fabric (unlike Docker, per the article) and they have a great redundant DB capability, sorely missing from other PaaSes, even k8s.

I have no doubt that docker will eventually catch up though.

Re: Lessons learned from using Docker Swarm mode in production

#54

Post by madmax96 »

ovi256 wrote: post #53
madmax96 wrote: post #30

Earlier quoted context omitted.

My experience with Kubernetes is limited, so take all this with a grain of salt. I've been using the integrated swarm since beta. The new integrated swarm is a real game-changer in that it is much simpler to use compared to other solutions. With swarm, it's simply: docker swarm init docker swarm join --token That being said, I found that Kubernetes offers more granularity in the level of control over the cluster. Tha…

I've had the same great, simple experience with Flynn. The terminal commands you give are barely different from Flynn's. And I like Flynn's capabilities better, at least for now. They've already figured out the routing fabric (unlike Docker, per the article) and they have a great redundant DB capability, sorely missing from other PaaSes, even k8s. I have no doubt that docker will eventually catch up though.

That's cool. I've never looked at Flynn, but you've motivated me to give it a look!

Re: Lessons learned from using Docker Swarm mode in production

#55

Post by justinsaccount »

madmax96 wrote: post #30
jahewson wrote: post #24

Honestly, you should try kubernetes. The experience is pretty much the same and the feature set is much more mature.

My experience with Kubernetes is limited, so take all this with a grain of salt. I've been using the integrated swarm since beta. The new integrated swarm is a real game-changer in that it is much simpler to use compared to other solutions. With swarm, it's simply: docker swarm init docker swarm join --token That being said, I found that Kubernetes offers more granularity in the level of control over the cluster. Tha…

People are working one this feature for kubernetes:

  kubeadm init master
  kubeadm join node --token=73R2SIPM739TNZOA
https://github.com/kubernetes/kubernetes/pull/30360
Post reply on HN