Live data from Hacker News

Why Kubernetes isn't using Docker's libnetwork

blog.kubernetes.io

21–30 of 48 posts

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

#21
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

Or just means Redhat went Docker crazy.

At some point they were being made fun of for being slow, old fashioned, stuck in the early 2000s. They have to be obviously for stabiliy, but you know word spreads. So around RHEL 7 time they went all crazy trying to show the tech world they are still hip and cool, looked around, saw what the cool kids were talking about -- Docker. So they got themselves some Docker. So now it is Docker, Docker, Docker all day every day.

Naturally now it is uncomfortable to say "yeah well LXC is there, can use that as well or instead of Docker", but that would kind of backpedaling on their Docker bet by having something that competes with it. So they are stripping it out.

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

#23
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.

You are right that both projects are monolithic (and of coz open-sourced), but it is unfair to compare a VC backed company with non-profit organization.

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

#25
post #17
post #15

Earlier quoted context omitted.

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.

The main dev does work for them and they thus get first class support, that helps! (It's not working as well on Debian for example, at least a few months back)

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

#26
post #9
post #8

Earlier quoted context omitted.

The team at CoreOS came to a similar conclusion: > Docker has demonstrated that it is on a path to include many facilities beyond basic container management, turning it into a complex platform. More than a year ago on their blog, https://coreos.com/blog/rocket/

I'm increasingly impressed with CoreOS, especially etcd, and more generally, using systemd for init. Not that difficult to get up and running either.

I am running Kubernetes on CoreOS in production. Have been very happy with the setup. Kubernetes docs and community are excellent.

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

#29

FWIW, it is coming from the very top. https://twitter.com/solomonstre/status/687773282104287232

Looooooooooool, what inflammatory shit did he say that he /didn't/ leave up considering what he HAS left up?

SHYKES, for the love of all your VC's money, shut your pie hole.

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

#30

FWIW, it is coming from the very top. https://twitter.com/solomonstre/status/687773282104287232

Solomon Hykes @solomonstre @kelseyhightower TLDR "no actual downside for Docker users, but it makes it hard to for us to embrace-extend-extinguish" Today at 3:08 PM
Post reply on HN