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

Docker for Mac with Kubernetes

docs.docker.com

Post reply on HN
Print view View original

91–100 of 169 posts

Re: Docker for Mac with Kubernetes

#91

Post by sandGorgon »

zenlikethat wrote: post #33
StavrosK wrote: post #26

Earlier quoted context omitted.

I don't know what any of those mean :(

EE = Enterprise Edition UCP = Universal Control Plane (web app to manage clusters and containers) HRM = Host routing mesh (I think). If I recall correctly, it’s used to control ingress to the cluster via virtual host routing, etc. They are paid Docker Inc. products. I worked for Docker once upon a time so I’m happy to hear there are happy customers :)

Docker has added ingress routing in 17.06 that works at a lower level than HTTP Routing Mesh. You should try that now.

Other than that, how have you found EE ? We have considered paying for it, but after seeing Docker Cloud at 15$ per node per month, we are considering switching to it.

Re: Docker for Mac with Kubernetes

#92

Post by dominotw »

tedmiston wrote: post #61
linkmotif wrote: post #55

So confused by all the posts from people who say they run Swarm because kubernetes is too complicated or is only for huge deployments. I’ve had all sort of difficulties installing Docker. By hand it’s not trivial to get a secure install. Docker machine is great except it’s often broken. The Docker machine dev team is a tired, understaffed bunch that’s always playing a sisyphean whack-a-mole against dozens of cloud pr…

Do you really find k8s useful for a single node deployment or were you just making an example? I haven't used but I have used DC/OS, Mesos, and Marathon extensively, which is not a setup I'd do for a small number of nodes personally.

>I have used DC/OS, Mesos, and Marathon extensively

Would you use DC/OS-marathon (vs k8s) now if you were to make that decision now.

I've heard that mesos stack is good for machine learning/big data stacks but how does marathon compare for deploying webapps.

Re: Docker for Mac with Kubernetes

#93

Post by dominotw »

justincormack wrote: post #19
watoc wrote: post #15

Earlier quoted context omitted.

I've never noticed this issue with the stable version. However I'm experiencing high CPU usage whenever I start minikube on my Mac. I just installed Docker edge. We'll see how it goes in the long run but so far with k8s enabled hyperkit uses 25% of a virtual core.

This is a Kubernetes issue, the same issue on Minikube and Docker for Mac. The Kube API server uses a lot of CPU when idle. We are trying to diagnose what is happening.

yea it cpu usage goes down if i disable kubernetes.

Re: Docker for Mac with Kubernetes

#94

Post by brown9-2 »

stephenr wrote: post #22

I don't understand the use-case here. You want to use Docker+Kubernetes but can't work out the bits to run it in VM's on your own?

I don’t get it either. minikube is trivially installed in my experience with homebrew.

Given that running docker on a Mac has been a long and bumpy journey, I’m not sure I’d want to bundle the two together.

What am I missing?

Re: Docker for Mac with Kubernetes

#95

Post by felipelemos »

alexellisuk wrote: post #39
justincormack wrote: post #18

Earlier quoted context omitted.

It is usable for the vast majority of users. If it is causing an issue please file a detailed bug report, with diagnostic ID, also try the Edge releases, and give some information about what you are actually running, for example how to replicate it. Most of the bug reports in that thread are totally unhelpful. Quite likely it is not even the same cause for different people, as some people said it was fixed on Edge wh…

I have 60-65% CPU usage at idle - it's not ideal for battery life but it is usable and I'd say it's easier to use than minikube (which is something that I also use a lot). This is very early for DfM + K8s - I'd say the usability outlays teething issues. If you want to help send in diagnostic reports for the Docker guys.

60% at idle is a big no no for laptops.

Re: Docker for Mac with Kubernetes

#96

Post by InTheArena »

perceptronas wrote: post #4

Docker for Mac is not usable today, because of high cpu due IO [1] [1] https://github.com/docker/for-mac/issues/1759

I've not had any problem with it, and the high high productivity win of being able to tell people just to turn Kubernetes in Docker on is amazing so far.

Right now, I am running 10 containers on my Mac, and my highest CPU in Intellej. Docker is running consistently with about 5-10% of the CPU.

Re: Docker for Mac with Kubernetes

#98

Post by lobster_johnson »

perceptronas wrote: post #4

Docker for Mac is not usable today, because of high cpu due IO [1] [1] https://github.com/docker/for-mac/issues/1759

I haven't run into that issue, but another issue that will likely trip up a lot of devs is the extremely slow shared volume support. [1] Mounting a database directory from the host is pretty much a no-go. Mounting source trees (e.g. React app with hot code reloading) less so, but still much slower than native. Many devs have resorted to workarounds such as NFS or rsync.

[1] https://github.com/docker/for-mac/issues/77

Re: Docker for Mac with Kubernetes

#99

Post by tokenizerrr »

linkmotif wrote: post #55

So confused by all the posts from people who say they run Swarm because kubernetes is too complicated or is only for huge deployments. I’ve had all sort of difficulties installing Docker. By hand it’s not trivial to get a secure install. Docker machine is great except it’s often broken. The Docker machine dev team is a tired, understaffed bunch that’s always playing a sisyphean whack-a-mole against dozens of cloud pr…

You're running on GKE. Of course that's easy, they're handling all the difficult parts for you! It's still not that difficult running it on your own servers, but there are many more pain points.

Please get some experience with that, then re-evaluate whether Docker or Kubernetes is easier for small deployments.

Re: Docker for Mac with Kubernetes

#100

Post by sandGorgon »

linkmotif wrote: post #79
drdaeman wrote: post #77

Earlier quoted context omitted.

> Kubernetes on the other hand is trivial with GKE How do I install GKE on my servers? ;) > By hand it’s not trivial to get a secure install. The default install (basically, adding a repo and apt-get install docker-ce on Debian and derivatives - trivial to automate with Ansible) is reasonably secure if you view Docker as a tool for packaging and task scheduling with some nice extras and don't buy the marketed isolati…

Thanks for the reply. I agree with what you say. I'm not tying to say people should all jump to k8s. Having options on the market is great. But I was trying to refute the notion that Kubernetes has no advantages unless you're running a huge cluster. My main points where: * It works great with 1 node. * It comes with many features that Swarm does not have that are useful even at 1 node (PersistentVolumes, StatefulSets…

Actually if you are using StatefulSets and PV, then kubernetes is a better fit for you.

However, Swarm is undeniably simpler to work with unless you have very specific requirements that only K8S provides. The yml file is incredibly simpler.

Docker Swarm is the Kotlin to Kubernetes' Java. It's a much pleasanter and much less intimidating way to build production systems that scale pretty well.

Kubernetes needs you to have load balancers setup which can talk K8S ingress. Bare metal setup for k8s is a huge effort (and I have stuck long enough on #sig-metal to know) as compared to Swarm.

You should try out Swarm - you might choose not to use it, but you will enjoy the experience.

Post reply on HN