Live data from Hacker News

Why Kubernetes isn't using Docker's libnetwork

blog.kubernetes.io

11–20 of 48 posts

Re: Why Kubernetes isn't using Docker's libnetwork

#11
post #4

I feel so silly but I can't help myself. The name 'Kubernetes' is so ugly and off-putting I hope I never have to use this software.

With all due respect, you don't only "feel" silly.

A catchy name, with fewer syllables, or fun acronym has some value does it not?

Re: Why Kubernetes isn't using Docker's libnetwork

#13
post #7

Nice to finally see it in writing: "Throughout this investigation Docker has made it clear that they’re not very open to ideas that deviate from their current course or that delegate control"

They showed the same attitude in https://github.com/docker/docker/issues/2112.

Continued insistence on that attitude virtually guarantees that they will lose out through refusal to solve problems that people actually have.

Re: Why Kubernetes isn't using Docker's libnetwork

#14
Docker is the monolith of container runtimes.

I think it’s a step backwards to have a monolithic application like Docker controlling your container runtime when you’ve gone through the effort of developing independent (micro)services.

Containerising software is the way forward and I think Kubernetes and CoreOS have demonstrated to have and support a long term vision.

Re: Why Kubernetes isn't using Docker's libnetwork

#15
post #12

Although this is reasonable its upsetting, I hope in time lxc software get less fragmented.. Docker really should have just gone with CNI.

LXC is deprecated from RHEL 7.x onward.[1] Doesn't that relegate it to "an Ubuntu thing" status?

1. https://access.redhat.com/articles/1365153

Re: Why Kubernetes isn't using Docker's libnetwork

#16
Kelsey, you are very, very, very patient with shykes.

Shykes, jesus christ, I've been in the deep with docker long enough to have watched you guys make really, really poor decisions and then slowly backpeddal and redesign around them as you move forward with UCP and Swarm and more.

Ever regret not admitting that Pods were a good idea?

Yeesh. Some day Docker's VCs are going to get together and take away his tweeting privileges. At least he's not doubled over defending himself in this particular thread.

Re: Why Kubernetes isn't using Docker's libnetwork

#17
post #15
post #12

Although this is reasonable its upsetting, I hope in time lxc software get less fragmented.. Docker really should have just gone with CNI.

LXC is deprecated from RHEL 7.x onward.[1] Doesn't that relegate it to "an Ubuntu thing" status? 1. https://access.redhat.com/articles/1365153

Pretty sure that is just RHEL being unintelligent as usual. LXC is not really related to Ubuntu in any real way other than they are looking to write a persistent daemon for it called LXD.

Re: Why Kubernetes isn't using Docker's libnetwork

#18
post #14

Docker is the monolith of container runtimes. I think it’s a step backwards to have a monolithic application like Docker controlling your container runtime when you’ve gone through the effort of developing independent (micro)services. Containerising software is the way forward and I think Kubernetes and CoreOS have demonstrated to have and support a long term vision.

This doesn't make sense. As long as docker works well most people don't care about what's under the hood. For example The Linux kernel is a monolith, but you wouldn't make the same argument about running your containers on Minix.
Post reply on HN