LXC stopped working (virbr0 issue), looking for solution or alternative?

Support Virtualization
1

Hello.

LXC has stopped working for me within the past 2-3 months. I recall using a container in earlier 2023 but I now have this issue:

sudo lxc-start -n base -F                                        1 ✘  3s  
lxc-start: base: ../src/lxc/network.c: netdev_configure_server_veth: 711 No such file or directory - Failed to attach "veth0QBLKF" to bridge "virbr0", bridge interface doesn't exist
lxc-start: base: ../src/lxc/network.c: lxc_create_network_priv: 3427 No such file or directory - Failed to create network device
lxc-start: base: ../src/lxc/start.c: lxc_spawn: 1840 Failed to create the network
lxc-start: base: ../src/lxc/start.c: __lxc_start: 2107 Failed to spawn container "base"
lxc-start: base: ../src/lxc/tools/lxc_start.c: main: 306 The container failed to start
lxc-start: base: ../src/lxc/tools/lxc_start.c: main: 311 Additional information can be obtained by setting the --logfile and --logpriority options

I want to keep using system containers to isolate my development environments, but I don’t want to ‘fight’ against LXC with complicated configs.

Is there an easy solution for this problem?

Or is there a better system container option that “just works” on Manjaro?

2

I suppose you are familiar with

An alternative could be

The majority of issues on Manjaro stable may be - if not completely, then for the most part - eliminated by using Manjaro unstable branch.

If you are - like most - using Manjaro stable branch you may benefit by switching to unstable - thus eliminating the delay between Manjaro stable and Arch stable.