Hacker News Reader

Comment by avhception | Hacker News Reader

It's sad that LXD (https://github.com/lxc/lxd) gets so little attention. It's a great compromise between a VM and a container as it doesn't have the 1:1 relation between container and process. I use it to great effect at $dayjob.

Not that it is an alternative to K8s in every scenario, but it should have gotten at least a mention in the intro section.

View on HN

You can achieve a similar effect in "standard" containers by running systemd as the entrypoint. This is how kind runs containers as k8s nodes. I agree it's a very handy scenario for many workloads.

This does makes me want to build "kilx" k8s inside lxd heh

I like this supervisord port written in golang.

https://github.com/ochinchina/supervisord

You can configure it like supervisord with a single config file,

https://riptutorial.com/docker/example/14132/dockerfile-plus...

But the golang version is much smaller / less deps and can be installed as a static binary.

Thanks for sharing this looks fantastic.

LXC/LXD is amazing tech. I use it at work and at home for quickly getting services up and running.

I still don't get where LXC/LXD shine. Is there a killer application for this tech?

Check out proxmox which supports kvm and lxd so it's easy to compare. lxd uses less resources and an image registry vs finding/building kvm cloud images.

I have a dedicated server at home running as an LXC host.

With an LXC client on my laptop I am able to launch instances without using local resources. The instance has profiles setup to add the containers to my local lan for ease of access.

Launching a new machines is only a few commands away.

Reply on news.ycombinator.com