Live data from Hacker News

Docker 19.03: Rootless Mode (Experimental)

github.com

41–45 of 45 posts

Re: Docker 19.03: Rootless Mode (Experimental)

#41

Earlier quoted context omitted.

Would you be willing to elaborate on the reason why you avoid kubernetes?

As a huge proponent of kubernetes for the enterprise world (a big part of my day job), I won’t touch it for small to medium sized projects. The cost of running a managed kubernetes is too expensive to justify for the benefits in these cases. And if you choose to self-manage to cut the money cost, it ends up being significantly more expensive from a time and sanity perspective.

What are the costs of a managed Kubernetes? I don't know if I understand what you mean, because most managed Kubernetes that I know are practically not, or just nominally more expensive in terms of resource cost. Like GKE, AKS, you don't pay for manager nodes, so it's actually a cost savings compared to running your own Kubernetes with kubespray or another method that leaves managing the control plane nodes up to you - managed Kubernetes is actually cheaper, if you're building for high availability.

Are you referring to the cost of migration (since most Kubernetes adopters are probably also learning K8s for the first time as well?)

Re: Docker 19.03: Rootless Mode (Experimental)

#42

Earlier quoted context omitted.

Hmmmm... I can't say I've ever looked a whole lot. Based on the replies in this thread though, I should probably just take the scripts I've got, make sure there's nothing sensitive in there, and throw them up on Github. Maybe I'll strip my SSH pubkey out of the too, so that we don't end up with a bunch of servers that I can log into :D

That would be cool! (And that's a yes for stripping your SSH key ;)

As a tangent... super curious about your username. I've been in the local Radarsat ground terminal and worked on some barely-related projects...

Re: Docker 19.03: Rootless Mode (Experimental)

#43
post #25

Earlier quoted context omitted.

I mean that it likely makes certain assumptions about how runc sets up containers which aren't true of LXC. I'm sure you could get CNI to work with LXC (in fact, someone might've already done that -- I'm not sure tbh) but it wouldn't be something you'd be able to drop-in without at least a bit of extra work. For instance, LXC's hooks run in different contexts to OCI hooks (though we recently discovered that runc runs…

> likely makes certain assumptions about how runc sets up containers Nope. CNI takes as parameters a “container ID” (any string) and a network namespace path. No knowledge is needed or implied about how those things fit with actual containers.

There are some circumstances where that might not work as seamlessly as possible (such as with user namespaces -- runc and LXC set those up slightly differently and run hooks in slightly different orders and contexts) but it wouldn't be too hard to get it to work. I did a quick search, and it turns out that making CNI work under LXC did require some patches (though I'm not sure if they were CNI or LXC patches -- the blog post doesn't link to either) but they were all merged a bit less than 2 years ago[1].

[1]: https://s3hh.wordpress.com/2017/10/19/cni-for-lxc/

Re: Docker 19.03: Rootless Mode (Experimental)

#44

Earlier quoted context omitted.

That would be cool! (And that's a yes for stripping your SSH key ;)

As a tangent... super curious about your username. I've been in the local Radarsat ground terminal and worked on some barely-related projects...

Haha awesome not often people comment on it.. a previous employer did some work on Radarsat-1 so the name was floating around in my circles a couple of decades ago when I was starting to make music and post on forums, I just started using it without much thought and it stuck

Re: Docker 19.03: Rootless Mode (Experimental)

#45

Earlier quoted context omitted.

I'm not the OP, but... Here's the scene: Most of the web projects I work on will never have a billion users. They might have 5, or 10. One or two have thousands. Several of them have 1 (me). Docker-compose works for me. I set up a container for my backend, a container for whatever's serving the static resources for the frontend, and a container for whatever databases are needed (Postgres, Redis, whatever). The databa…

Out of curiosity, have you ever used Traefik? At work we're using Docker Swarm (because we needed more power than a single server could give us but Kubernetes seemed excessive) with Traefik and it works beautifully.

Hey Unicornfinder. Please join us at the community forum if you haven't already. And, thanks for the mention! We hope to get to know you more, on the forum. https://community.containo.us
Post reply on HN