LXD
LXD is a next generation system container manager. It offers a user experience similar to virtual machines but using Linux containers instead.
- Developed at Virtualization:containers
- Sources inherited from project openSUSE:Factory
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:Rebuild/lxd && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| lxd-4.2.tar.gz | 0025297836 24.1 MB | |
| lxd-4.2.tar.gz.asc | 0000000833 833 Bytes | |
| lxd-rpmlintrc | 0000000280 280 Bytes | |
| lxd.changes | 0000011799 11.5 KB | |
| lxd.dnsmasq | 0000000310 310 Bytes | |
| lxd.keyring | 0000004201 4.1 KB | |
| lxd.service | 0000000811 811 Bytes | |
| lxd.spec | 0000011494 11.2 KB | |
| lxd.sysctl | 0000001023 1023 Bytes |
Revision 16 (latest revision is 59)
Dominique Leuenberger (dimstar_suse)
accepted
request 812999
from
Aleksa Sarai (cyphar)
(revision 16)
- Update to LXD 4.2. The full upstream changelog is available from: https://discuss.linuxcontainers.org/t/lxd-4-2-has-been-released/8071 bsc#1172605 + VLAN filtering on bridges * Expanded network state information + Support for custom search domains + New IPv4 and IPv6 columns in network lists * mips & riscv64 support for containers and s390x support for VMs * Using pidfds for all container subprocesses * LVM volumes only active when needed + DB query tracing support * Better cluster life-cycle handling * Cleaned up database functions
Comments 3
Thanks a lot to everyone for making this possible. <3
Tumbleweed 32bit LXD container not getting IPv4 address.
I am running LXD on a Tumbleweed 32bit x86 VirtualBox host. When launching containers I get an IPv4 address using default bridge for Debian, Alpine containers. If I launch a Tumbleweed container I am not getting an IPv4 address, only IPv6. When executing
ss -lntuinside Tumbleweed container I cannot see port 68 (dhcp client) as listening. The problem exist on a Tumbleweed 32bit physical host as well, but it is not an issue on aarch64 (Raspberry Pi 4). Thank you.Can you open a bugzilla entry for this? Comment threads in OBS are not the right place for bug reports.