DietPi as LXC container

General Discussion
1

hi everybody. I want to install dietpi as an lxc container.
I installed debian, then installed dietpi from above using this script, but in the end the system can’t find network device. help me solve the problem. I also tried to unpack DietPi_Container-x86_64-Bullseye.img.xz, also there is no network device.

[ 0.000000] eth0: renamed from vethJapgw2
[ 0.000000] br0: port 2(vethASdTvZ) entered blocking state
[ 0.000000] br0: port 2(vethASdTvZ) entered forwarding state

root@DietPi:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: tunl0@NONE: mtu 1480 qdisc noop state DOWN group default qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
3: eth0@if41: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 52:54:00:23:84:cf brd ff:ff:ff:ff:ff:ff link-netnsid 0
inet6 fe80::5054:ff:fe23:84cf/64 scope link
valid_lft forever preferred_lft forever

2

Using the forum search should give similar topics like Create a LXC container - #6 by StephanStS

3

I didn’t find the answer I need

4

I assume that you tried to use Supported hardware - DietPi.com Docs on top of a plain debian lxc container.
I assume that this does not work due to networking, I guess I had similar experiences on Proxmox.

I did not experiment with the image DietPi_Container-x86_64-Bullseye.img.xz for this lxc purpose.

If you want to use Proxmox, I propose to follow DietPi LXC containers in Proxmox – DietPi Blog. This works for my Proxmox installation.
I had also experiences with a lxc container running only an MQTT server which needed a quite long time to start Mosquitto (lxc container took about 2 minutes compared to a small VM starting Mosquitto in < 30 sec). I do not know what was the reason for that, a Node-RED running in an lxc container e.g. works well.
So I propose in case of similar anomalies to compare your lxc software installation to a VM based software installation.