Live data from Hacker News

Launch HN: Nestybox (YC S20) – Containers beyond microservices

news.ycombinator.com

91–100 of 112 posts

Re: Launch HN: Nestybox (YC S20) – Containers beyond microservices

#91

can you run kubernetes in nestybox ? entirely within the container ? if you can do this (and build a great experience around it), you have a winner. k3d.io does it somewhat...but not all the way. Updates,rollbacks, etc - everything that a sysadmin need.

> can you run kubernetes in nestybox ? entirely within the container ? > if you can do this (and build a great experience around it), you have a winner. Genuine question. I'm not that familiar with Kubernetes. Can you explain the pain this solves? What is this winning at?

There is plenty of info on Kubernetes (K8s) on the web, so I would start there. As far as running K8s inside Docker containers though, the use case would be one in which you want to run multiple isolated K8s clusters on a single host. One way is to use VMs, but recently people are resorting to using containers for this purpose due to their ease & efficiency. It's in the latter that Sysbox really helps, because it's capable of creating a container that runs K8s easily and with proper isolation. Typical use cases are testing, CI/CD, learning. But I would not discount this moving into production use cases in the future as the technology matures.

Re: Launch HN: Nestybox (YC S20) – Containers beyond microservices

#92
the docker installation that rhel uses carries small patches that enable one to build containers that run with systemd as init with ease, without the user having to do anything special (or run with privilege), its runtime sets everything up for you correctly. I've built and run them, so I know they work.

RedHat wanted docker to take them, but Docker refused.

Re: Launch HN: Nestybox (YC S20) – Containers beyond microservices

#93

the docker installation that rhel uses carries small patches that enable one to build containers that run with systemd as init with ease, without the user having to do anything special (or run with privilege), its runtime sets everything up for you correctly. I've built and run them, so I know they work. RedHat wanted docker to take them, but Docker refused.

Didn't know that. But it makes sense given that podman already supports it. Btw, i did a quick search but couldn't find anything on this (docker's systemd support in rhel). If you happen to know where to find these patches, please send them my way. Thanks.

Re: Launch HN: Nestybox (YC S20) – Containers beyond microservices

#95
This looks interesting and promising. There are definitely use-cases to run docker in docker. We are running some open source project that leverages dockers heavily, let's see if we can collaborate to make things work end-to-end, I believe that would be beneficial for both communities.

Re: Launch HN: Nestybox (YC S20) – Containers beyond microservices

#96
post #95

This looks interesting and promising. There are definitely use-cases to run docker in docker. We are running some open source project that leverages dockers heavily, let's see if we can collaborate to make things work end-to-end, I believe that would be beneficial for both communities.

Thank you. Please reach out to us through email/slack. Would love to hear more.

Re: Launch HN: Nestybox (YC S20) – Containers beyond microservices

#97
post #94

what's the difference with say lxc | lxd ?

Please see our response to a similar question below. Hope that helps. Thanks.

"The main difference is that Sysbox is OCI-based, so it works with Docker/containerd and hopefully K8s soon (we are working on the latter). Also, correct me if I am wrong, but I don't believe LXD runs K8s inside without privileged containers. Having said this, I know LXD and Sysbox use many of the same OS-virtualization techniques to do what they do. And in fact we owe much of the work we've done to the ground-work done by the good folks at Canonical/LXD."

Re: Launch HN: Nestybox (YC S20) – Containers beyond microservices

#100

Any reason why sysbox is only supported on Ubuntu and not say RHEL / CentOS / Fedora?

Ubuntu carries a few things that Sysbox relies on: a couple that come to mind are the shiftfs module (which Sysbox uses to enable the user-namespace in containers without requiring Docker to be set in userns-remap mode) and a kernel patch that allows overlayfs mounts from within a user-namespace (since the Docker running inside the container uses overlayfs mounts for its inner images). Having said this, we are looking at ways of overcoming these requirements to extend Sysbox to more distros; it's one of the most asked features.
Post reply on HN