LXC
lxd
| LXC | lxd | |
|---|---|---|
| 7 | 29 | |
| 4,449 | 3,952 | |
| 0.9% | - | |
| 9.2 | 9.9 | |
| 5 days ago | 10 months ago | |
| C | Go | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
LXC
-
LXD Moves into Canonical
I hope this doesn't affect LXC negatively.
LXC and LXD share plenty of contributors.
https://github.com/lxc/lxc/graphs/contributors
https://github.com/canonical/lxd/graphs/contributors
I use an "unprivileged LXC container" setup on several Debian bullseye hosts. It works fantastic, and each LXC container feels like a real server.
Compare that to Docker's "one-container-one-process" philosophy, reinventing the wheel by awkwardly composing multiple containers.
-
Support for Android apps
There is an issue with lxc as stated here: https://github.com/lxc/lxc/issues/4283 and https://github.com/Vanilla-OS/apx/issues/118
-
LXC & AD
I'm currently attempting to enroll my Ubuntu (20.04) (Unprivileged) LXC hosts to my windows AD server but am having difficulty. I'm using SSSD and KRB5 to manage the user directory and authentication. Once joining the domain with realmd, all seems ok, I can use the id command, etc to lookup users and groups and the host appears in Windows Users and Computers. The issue I'm having is with authentication, I believe it to be related to this issue however I don't entirely understand the solution and can't seem to find much else on the matter (Note the method I'm using works fine on full VMs). Would anybody please be able to provide more clarity in layman's terms?
-
LXC and LXD: a different container story
I don't recall having to do any uid/gid fixup last time I made an unprivileged container. I did have to prepare the unprivileged host user, of course, by reserving a range of subordinate uids/gids (/etc/sub?id) and configuring a virtual network interface limit (/etc/lxc/lxc-usernet).
To create the container, I did this:
lxc-create -t download -n -- -d debian -r bullseye -a amd64
Note that this runs the 'download' template, which (IIRC) is better suited to unprivileged containers than the 'debian' template is. The 'download' template will list its available distros if you do this:
lxc-create -t download -n -- --list
Note that some versions of lxc-create may fail with a keyserver error because sks-keyservers.net died somewhat recently. Workaround: DOWNLOAD_KEYSERVER=hkp://keyserver.ubuntu.com lxc-create
https://github.com/lxc/lxc/issues/3894
-
Lxc container still gives Cannot open TUN/TAP dev /dev/net/tun: Operation not permitted after following graysky's edit of wiki
Found this issue and edited the config file of the lxc container:
-
How to - Create LXC containers FROM Docker and OCI images
and on this thread... an different approach is described
-
Finally joining the club
https://github.com/lxc/lxc/issues/1629#issuecomment-311379508
lxd
-
LXD is now under Canonical
The expected changes are: - https://github.com/lxc/lxd will now become https://github.com/canonical/lxd - https://linuxcontainers.org/lxd will disappear and be replaced with a mention directing users to https://ubuntu.com/lxd - The LXD YouTube channel will be handed over to the Canonical team - The LXD section on the LinuxContainers community forum will slowly be sunset in favor of the Ubuntu Discourse forum run by Canonical - The LXD CI infrastructure will be moved under Canonical’s care - Image building for Linux Containers will no longer be relying on systems provided by Canonical, limiting image building to x86_64 and aarch64.
-
LXC images download
Hello community, it seems LXC images for arm7l/armhf are no longer available, not from the official Turris mirror nor from LinuxContainers.org (https://linuxcontainers.org/lxd/). Any solution or alternative for people like me heavily relying on the Turris Omnia to run LXC containers? Thanks.
- Creating .deb files from the source
- https://linuxcontainers.org › latest about LXD projects documentation
-
LXC containers not accessible when Internet is down
here you go idiot down voters https://github.com/lxc/lxd/issues/10470
What are some alternatives?
Portainer - Making Docker and Kubernetes management easy.
kata-containers - Kata Containers is an open source project and community working to build a standard implementation of lightweight Virtual Machines (VMs) that feel and perform like containers, but provide the workload isolation and security advantages of VMs. https://katacontainers.io/
Docker Compose - Define and run multi-container applications with Docker
kubevirt - Kubernetes Virtualization API and runtime in order to define and manage virtual machines.
Docker - Notary is a project that allows anyone to have trust over arbitrary collections of data
firecracker-container
Docker Swarm - Source repo for Docker's Documentation
firecracker-containerd - firecracker-containerd enables containerd to manage containers as Firecracker microVMs
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
podman-desktop-companion - Podman desktop companion
Harbor - An open source trusted cloud native registry project that stores, signs, and scans content.
podman - Podman: A tool for managing OCI containers and pods.