Re:Why Kubernetes isn't using Docker's libnetwork
by fidget on Thursday January 14, 2016 @04:58PM
(#10904913)
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"
[ Parent
| on HN ]
Re:Why Kubernetes isn't using Docker's libnetwork
by namsral on Thursday January 14, 2016 @05:09PM
(#10905032)
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/
Re:Why Kubernetes isn't using Docker's libnetwork
by magicmu on Thursday January 14, 2016 @05:17PM
(#10905110)
I'm increasingly impressed with CoreOS, especially etcd, and more generally, using systemd for init. Not that difficult to get up and running either.
Re:Why Kubernetes isn't using Docker's libnetwork
by manojlds on Friday January 15, 2016 @12:03AM
(#10907314)
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
by nwmcsween on Friday January 15, 2016 @06:22PM
(#10913057)
Talk about the pot calling the kettle black.
Re:Why Kubernetes isn't using Docker's libnetwork
by btilly on Thursday January 14, 2016 @05:26PM
(#10905200)
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.