HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
automaticserver
lxe
Go2018–2021
automaticserver / lxe

lxe

Kubernetes CRI shim for lxd. Initially contributed by Automatic Server AG (http://www.automatic-server.com)

4Distinct people
4Mentions
0Explicit recommenders
231GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Kubernetes CRI shim for lxd. Initially contributed by Automatic Server AG (http://www.automatic-server.com)

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:03:16 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year4 dated mentions

Observed mentions: 2018-10-04 12:56:01 UTC to 2021-08-28 01:04:33 UTC.

0122018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC110
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101

What Hacker News says

4 sources
this seems like such a really good baseline for a home-cloud. there's such good host infrastructure here. i'm such a huge Debian lover but there's so much more required to turn it into a decent host environment, and Proxmox covers so much ground to do just that. but i still want Kubernetes as my primary interface atop it. since LXC is the primary container system on Proxmox (and a damned fine one at that), it seems like one might be able to make something like LXE[1] run, as a shim, to provide a Container Runtime Interface & start running kubelet (the thing that runs containers) atop that. [1] https://github.com/automaticserver/lxe
In Proxmox VE 7.0 Released
LXC+LXD is one of the most undervalued container technologies out there. It can do a lot of cool things (like live migration via criu), and is IMO more production ready than Docker ever was. For those wondering about the distinction between "system" containers and "app" containers, the difference is user namespacing -- I think we should stop using the naming difference but instead go with specifying that the containers "full user name spacing". User namespacing is the "magic sauce" for projects like Podman and a related project Buildah which builds images without root privileges -- the combination of user namespaces and FUSE. BTW for those wondering if container orchestrators like Kubernetes will be shaken by this -- they very likely won't. Kubernetes has sidestepped this problem by introducing and relying on RuntimeClass[0], which allows
Read the rest
you to swap out the runtime that's running underneath kubernetes. In fact, there is already a shim being worked on[1]. [EDIT] - While I'm here talking about container tech, please check out containerd[2]. It's been my runtime of choice for a very long time, has been very well maintained, and received many of the really advanced features first (ex. untrusted runtimes). IMO it should be the default container runtime of k8s. [0]: https://kubernetes.io/docs/concepts/containers/runtime-class... [1]: https://github.com/automaticserver/lxe [2]: https://github.com/containerd
In Making containers safer

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.