To Proxmox or not to Proxmox

Configuration
121

Just run nano /etc/pve/lxc/105.conf in the Proxmox web shell and change cgroup to cgroup2

Also, what zigbee coordinator are you using?

122

If youโ€™re using a USB coordinator, you could try and replace your last 4 lines in 105.conf

with this (change cgroup accordingly)

lxc.cgroup2.devices.allow: c 188:* rwm
lxc.mount.entry: /dev/serial/by-id               dev/serial/by-id         none bind,optional,create=dir
lxc.mount.entry: /dev/ttyUSB0                    dev/ttyUSB0             none bind,optional,create=file
lxc.mount.entry: /dev/ttyACM0                    dev/ttyACM0             none bind,optional,create=file

to pass it into the LXC. If it works for you, itโ€™s much cleaner than autodev

1 Like
123

At the moment im using a Conbee II. just waiting for ZZH CC2652R to come back in stock as I would like to move from ZHA to ziggbee2mqtt

1 Like
124

Thanks for all these tips. Maybe it will help with my current issue with Danalock zigbee loosing connection to HA between 5am and 6am every day (cant see anything in logs file on Proxmox or HA that indicate where the issue lies)

125

Iโ€™m using Tubeโ€™s USB coordinator, IMHO, Itโ€™s the best. He has a waiting list that heโ€™s going through pretty quick.

1 Like
126

Thanks. I will take a look :slight_smile:

127

@tteck sorry to bother you again. I have tried replacing the last 4 lines as suggested, power cycled the LXC but ZHA throws an error:

Retrying setup: [Errno 2] could not open port /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2120494-if00: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik

When I go to console for the lxc and browse to /dev/serial/by-id I dont see anything in the path. When I browse to same directory from the node I see the following device:

usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2120494-if00

Any suggestions? (just to confirm, this is on PVE 6 still - thought I would make the change before upgrading to 7).
Thanks

128

Did you change cgroup2 to cgroup?

129

I did, removed the 2 on that line

130

Hate that didnโ€™t work. May need 189 also? Guess itโ€™s autodev for now.

131

ok cool, I will try adding the following:

lxc.cgroup.devices.allow: c 188:* rwm
lxc.cgroup.devices.allow: c 189:* rwm
lxc.mount.entry: /dev/serial/by-id               dev/serial/by-id         none bind,optional,create=dir
lxc.mount.entry: /dev/ttyUSB0                    dev/ttyUSB0             none bind,optional,create=file
lxc.mount.entry: /dev/ttyACM0                    dev/ttyACM0             none bind,optional,create=file
1 Like
132

@tteck unfortunatly that didnt work. but i have found the following thread and will try post 6 suggestion:

https://forum.proxmox.com/threads/usb-pass-through-in-lxc-container.73742/

133

@tteck Thanks for your scripts!

I run HA in a virtenv in a LXC and didnโ€™t think of putting it in a docker LXC. I use docker LXCs for a couple of things due to the smaller footprint etc compared to a KVM.

Going to see how it goes and probably will migrate it over as I am fed up with the dependencies issues.

Thanks again!

mb

1 Like
134

@tteck thanks for all your help.

Did the upgrade today. Had a brown trousers moment when PVE wouldnโ€™t come back online. The server is running headless so a frantic flurry of plugging into a TV, hooking up keyboard and network and diagnosing a kernel panic stopping PVE 7 from booting. Managed to find the fix by running โ€˜ dpkg --configure -aโ€™ and starting install again (whilst no longer headless) and everything booted ok. I switched cgroup to cgroup2 in all LXC containers and up and running.
Before doing the upgrade I used your VM script and restored HA to a new VM to get round any potential issues with the Conbee II mapping to USB pass through. Now to move back to an LXC :grin:

Also ordered and paid for one of Tubes USB coordinators so canโ€™t wait for that to come :grin:

1 Like
135

LXC is the grandfather of Docker, and is a container solution, not an hypervisor aka fully virtualization. Such as Docker it share the CPU and the Memory and is subjected to evasion via the filesystem, the process and memory calls.

At the end it is possible to run Docker inside an LXContainer. (nesting)

Proxmox and LXC could passthrough devices such as anything USB, PCI and harddrive like you could do with KVM.

1 Like
136

BLXC is the grandfather of Docker, and is a container solution, not an hypervisor aka fully virtualization. Such as Docker it share the CPU and the Memory and is subjected to evasion via the filesystem, the process and memory calls.

Agreed - to me LXC is for OS virtualisation and docker is for an app. HA is โ€˜justโ€™ a python app, but I prefer a LXC as HA feels a lot more than one app. That said, I am going to move over to docker very soon for HA.

mb

137

Combined all Proxmox helpers into 1 repo,

5 Likes
138

Hi I note that you have reviewed you scripts. I have tried to install the Proxmox Haso VM , however i have problems in installing this issue root@pve:~# bash -c โ€œ$(wget -qLO - https://raw.githubusercontent.com/tteck/Proxmox/main/haos_vm.sh)โ€
[INFO] Using โ€˜local-lvmโ€™ for storage location.
[INFO] Container ID is 103.
Getting URL for latest Home Assistant disk imageโ€ฆ
Downloading disk imageโ€ฆ
Checking for unzip commandโ€ฆ
Installing Unzipโ€ฆ
Reading package listsโ€ฆ Done
Reading package listsโ€ฆ Done
Building dependency treeโ€ฆ Done
Reading state informationโ€ฆ Done
E: Unable to locate package unzip
[ERROR] 100@117 Unknown failure occured. text`

Any idea how to solve it Running Proxmox 7 I appreciated that i can install and LXC version but i am only happy with the supervised version. Any advise would be appreciated.

139

Can you try it again

Edit: I just ran the script, and it installed without issues on Proxmox 7.0-11

140

@tteck I have gone to install a new LXC of HA from GitHub - tteck/Proxmox: Proxmox Helper Scripts but get the following error message:

INFO] Using 'hdd2-img' for storage location.
[INFO] Container ID is 114.
Updating LXC template list...
Downloading LXC template...
Creating LXC container...
Starting LXC container...
Setting up container OS...
Updating container OS...
E: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://ftp.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://ftp.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
[ERROR:LXC] 100@35 Unknown failure occured.
[ERROR] 100@167 Unknown failure occured.

Any suggestions? Just an FYI, I tried Whiskers script and also get the same problem there to on Proxmox 7.0-11 (non subscription with all the latest installs).

EDIT hmmmmmm I just ran the install for Zigbee2MQTT container and get similar:

root@Proxmox2:/opt# bash -c "$(wget -qLO - https://raw.githubusercontent.com/tteck/Proxmox/main/pve7_zigbee2mqtt_container.sh)"
[INFO] Using 'hdd2-img' for storage location.
[INFO] Container ID is 114.
Updating LXC template list...
Downloading LXC template...
Creating LXC container...
Starting LXC container...
Setting up Container OS...
Updating Container OS...
E: Repository 'http://security.debian.org buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://ftp.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
E: Repository 'http://ftp.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
[ERROR:LXC] 100@35 Unknown failure occured.
[ERROR] 100@164 Unknown failure occured.