# lxc Published articles for lxc. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Incus/LXC: contenedores de sistema en Linux DevFeed: [Incus/LXC: contenedores de sistema en Linux]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-03T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Containers](), [Linux](), [Command-line interface](), [API](), [Proxmox](), [Docker](), [qemu](), [podman]() Tags: [api](), [cli](), [containers](), [docker](), [linux](), [lxc](), [proxmox](), [qemu](), [rest](), [ssh](), [storage]() ### AI overview This Spanish-language tutorial explains Incus as a Linux Containers system-container and lightweight hypervisor manager built on LXC. It describes its origins as a community fork of LXD, compares system containers with application containers and virtual machines, and outlines how Incus differs from Proxmox, Docker, and Podman. ### Source excerpt Incus gestiona contenedores de sistema con LXC: instalación, incus launch, storage pools y redes, y cuándo elegirlo frente a Docker o una VM. ## Home Assistant: domótica autoalojada DevFeed: [Home Assistant: domótica autoalojada]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-03T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Home Assistant](), [Proxmox](), [Open Source](), [USB](), [Kernel]() Tags: [home-assistant](), [hub](), [kvm](), [lxc](), [os](), [proxmox](), [usb](), [vlan]() ### AI overview A Spanish tutorial explains how to self-host Home Assistant OS as a virtual machine on Proxmox. It recommends a full VM rather than LXC, discusses the Supervisor and add-ons, warns users to inspect community scripts, and covers updates, USB passthrough, dashboard access, and network isolation. ### Source excerpt Instala Home Assistant OS como VM en Proxmox, por qué conviene evitar el LXC, primeros pasos con el dashboard y cómo aislar tu domótica en su propia VLAN. ## Sponsored Post: G-Core Labs, Close, Wynter, Pinecone, Kinsta, Bridgecrew, IP2Location, StackHawk, InterviewCamp.io, Educative, Stream, Fauna, Triplebyte DevFeed: [Sponsored Post: G-Core Labs, Close, Wynter, Pinecone, Kinsta, Bridgecrew, IP2Location, StackHawk, InterviewCamp.io, Educative, Stream, Fauna, Triplebyte]() Original publisher: [Read original article]() Author: HighScalability Team Published: 2022-06-10T15:39:03Z Content type: article Language: en Sources: [High Scalability](), [High Scalability]() Topics: [DevOps](), [site-reliability-engineer](), [Databases](), [Monitoring](), [Ansible](), [hosting](), [Linux](), [PHP](), [JavaScript](), [NoSQL](), [WordPress](), [Ubuntu]() Tags: [ansible](), [databases](), [debian](), [devops](), [hosting](), [javascript](), [linux](), [lxc](), [monitoring](), [nosql](), [php](), [site-reliability-engineer](), [sponsored](), [sponsored-post](), [ubuntu](), [wordpress]() ### AI overview A sponsored post presents hiring and promotional opportunities from several technology companies, including Site Reliability Engineer, DevOps Engineer, SysOps Engineer, and JavaScript Developer roles. It highlights experience with databases, infrastructure, backend services, Linux, PHP, Ansible, LXC, hosting, WordPress, and JavaScript. ### Source excerpt Who's Hiring? Close is building the sales communication platform of the future and we're looking for a Site Reliability Engineer to help us accomplish that goal. If you have a passion for databases (both SQL and NoSQL), significant experience building, managing, and monitoring infrastructure, databases, and backend services at scale and want to work with a rag-tag team of hardworking, but humble humans, then come check us out! Wynter is looking for system administrators, engineers, and developers to join its research panel. Participate in research surveys, get paid ($90-$180/hr) for your feedback and comments. Super low key commitment, 10-15 mins per survey. Learn more and sign up. DevOps Engineer: At Kinsta, we set out to create the best managed hosting platform in the world. If you are an experienced DevOps Engineer who is constantly looking for ways to innovate and improve, we might just be the place for you! As Kinsta's DevOps Engineer, you will be instrumental in making sure that our infrastructure is always on the bleeding edge of technology, remaining stable and high-performing at all times. If you love working with Linux, have a background in PHP, and have worked with cutting-edge technologies, such as Ansible and LXC, check us out and apply here. SysOps Engineer: As Kinsta's SysOps Engineer, you'll play a key role in caring for the health of our servers, preventing issues, and responding immediately to mitigate any problems in our infrastructure. If you have experience in hosting and with the WordPress stack, have worked with Ubuntu or Debian-based systems, and cutting-edge technologies, such Ansible and LXC, you should definitely check us out and apply here! JavaScript Developer: Kinsta's Development Team aims to create truly effective solutions for our customers and our internal teams. We believe the only way to maintain and scale our standards is to focus on quality code. If you are a talented JavaScript developer and you would like to work with an owner ## CVE-2019-5736 and the Security Meaning of Privileged Containers DevFeed: [CVE-2019-5736 and the Security Meaning of Privileged Containers]() Original publisher: [Read original article]() Author: Christian Brauner Published: 2019-02-11T23:00:00Z Content type: article Language: en Sources: [Personal blog of Christian Brauner]() Topics: [container](), [Containers](), [vulnerability](), [Exploit](), [Security](), [implementation]() Tags: [containers](), [cve](), [exploit](), [lxc](), [runc](), [security](), [vulnerability]() ### AI overview The article examines CVE-2019-5736, a vulnerability that could let a malicious container overwrite the host runc binary and gain root-level code execution. It then develops a more precise definition of privileged containers based on whether ID 0 has the same semantics inside and outside the container. ### Source excerpt Introduction (CVE-2019-5736) ## Running Docker Swarm inside LXC (outdated) DevFeed: [Running Docker Swarm inside LXC (outdated)]() Original publisher: [Read original article]() Author: andreacorbellini Published: 2016-04-13T18:00:00Z Content type: tutorial Language: en Sources: [Andrea Corbellini]() Topics: [Docker](), [Tutorial](), [Containers](), [Development](), [Security]() Tags: [apparmor](), [article](), [containers](), [distributed-computing](), [docker](), [information-technology](), [lxc](), [security](), [shell](), [swarm](), [ubuntu]() ### AI overview This outdated tutorial explains how to run legacy Docker Swarm inside LXC containers using a preferred setup with AppArmor disabled, Docker OverlayFS storage, and etcd discovery. It notes that newer Docker Swarm does not work in LXC as described. ### Source excerpt UPDATE: This article was written in 2016 and refers to a version of Docker Swarm that is now known as "legacy Swarm". The newer Docker Swarm won't work in LXC as described in this article. I've been using Docker Swarm inside LXC containers for a while now, and I thought that I could share my experience with you. Due to their nature ... ## Are LXC and Docker secure? DevFeed: [Are LXC and Docker secure?]() Original publisher: [Read original article]() Author: andreacorbellini Published: 2015-02-20T16:36:00Z Content type: article Language: en Sources: [Andrea Corbellini]() Topics: [Security](), [Containers](), [Docker](), [Architecture & Design](), [Linux Kernel]() Tags: [cgroups](), [configuration](), [containers](), [docker](), [information-technology](), [linux-kernel](), [lxc](), [security]() ### AI overview This article examines the security boundaries of LXC and Docker, explaining what container isolation provides, what it does not provide, and how default configuration affects the ability to run untrusted code. ### Source excerpt Since its initial release in 2008, LXC has become widespread among servers. Today, it is becoming the preferred deployment strategy in many contexts, also thanks to Docker and, more recently, LXD. LXC and Docker are used not only to achieve modular architecture design, but also as a way to run untrusted code in an isolated environment. We can agree that the LXC and Docker ...