mirror of
https://github.com/community-scripts/ProxmoxVE.git
synced 2026-02-05 00:29:55 +03:00
Zigbee2MQTT LXC cannot be created #266
Closed
opened 2026-02-04 17:32:00 +03:00 by OVERLORD
·
46 comments
No Branch/Tag Specified
main
github-action-update-changelog
pr-update-app-files
docker_deb13
feat/cloudinit-sshkeys
feat/sqlserver2025
automated/update-github-versions
add-script-opencloud-1770212555
add-script-openclaw-1770212634
github-action-archive-changelog
update_apps_tool
add-script-wishlist-1770193085
MickLesk-patch-2
add-script-writefreely-1770188758
add-script-wealthfolio-1770143943
fix/vaultwarden-update-script
remove_memos
disable_npm
feature/codeberg-functions-forgejo-readeck
add-script-rustypaste-1770019426
add-script-kitchenowl-1770017260
fix/2fauth-php-version
tools_func_addcodeberg
CrazyWolf13-patch-2
add-script-shelfmark-1769790178
CrazyWolf13-patch-1
add-script-ampache-1769790139
add-script-languagetool-1769790155
remove_php_deps
ref_koilection
fix/php-module-improvements
tremor021-patch-1
fix/open-archiver-meilisearch-migration
cloudflare_dns
MickLesk-patch-1
michelroegl-brunner-patch-2
fix/version-display
fix/debian13-root-ownership
feat/interactive_prompts
feature/smart-error-recovery
core_stable
update_docs
refactor/tools-func-stability
certbot_npm
2026-02-03
2026-02-02
2026-02-01
2026-01-31
2026-01-30
2026-01-29
2026-01-28
2026-01-27
2026-01-26
2026-01-25
2026-01-24
2026-01-23
2026-01-22
2026-01-21
2026-01-20
2026-01-19
2026-01-18
2026-01-17
2026-01-16
2026-01-15
2026-01-14
2026-01-13
2026-01-12
2026-01-11
2026-01-10
2026-01-09
2026-01-08
2026-01-07
2026-01-06
2026-01-05
2026-01-04
2026-01-03
2026-01-02
2026-01-01
2025-12-31
2025-12-30
2025-12-29
2025-12-28
2025-12-27
2025-12-26
2025-12-25
2025-12-24
2025-12-23
2025-12-22
2025-12-21
2025-12-20
2025-12-19
2025-12-18
2025-12-17
2025-12-16
2025-12-15
2025-12-14
2025-12-13
2025-12-12
2025-12-11
2025-12-10
2025-12-09
2025-12-08
2025-12-07
2025-12-06
2025-12-05
2025-12-04
2025-12-03
2025-12-02
2025-12-01
2025-11-30
2025-11-29
2025-11-28
2025-11-27
2025-11-26
2025-11-25
2025-11-24
2025-11-23
2025-11-22
2025-11-21
2025-11-20
2025-11-19
2025-11-18
2025-11-17
2025-11-16
2025-11-15
2025-11-14
2025-11-13
2025-11-12
2025-11-11
2025-11-10
2025-11-09
2025-11-08
2025-11-07
2025-11-06
2025-11-05
2025-11-04
2025-11-03
2025-11-02
2025-11-01
2025-10-31
2025-10-30
2025-10-29
2025-10-28
2025-10-27
2025-10-26
2025-10-25
2025-10-24
2025-10-23
2025-10-22
2025-10-21
2025-10-20
2025-10-19
2025-10-18
2025-10-17
2025-10-16
2025-10-15
2025-10-14
2025-10-13
2025-10-12
2025-10-11
2025-10-10
2025-10-09
2025-10-08
2025-10-07
2025-10-06
2025-10-05
2025-10-04
2025-10-03
2025-10-02
2025-10-01
2025-09-30
2025-09-29
2025-09-28
2025-09-27
2025-09-26
2025-09-25
2025-09-24
2025-09-23
2025-09-22
2025-09-21
2025-09-20
2025-09-19
2025-09-18
2025-09-17
2025-09-16
2025-09-15
2025-09-14
2025-09-13
2025-09-12
2025-09-11
2025-09-10
2025-09-09
2025-09-08
2025-09-07
2025-09-06
2025-09-05
2025-09-04
2025-09-03
2025-09-02
2025-09-01
2025-08-31
2025-08-30
2025-08-29
2025-08-28
2025-08-27
2025-08-26
2025-08-25
2025-08-24
2025-08-23
2025-08-22
2025-08-21
2025-08-20
2025-08-19
2025-08-18
2025-08-17
2025-08-16
2025-08-15
2025-08-14
2025-08-13
2025-08-12
2025-08-11
2025-08-10
2025-08-09
2025-08-08
2025-08-07
2025-08-06
2025-08-05
2025-08-04
2025-08-03
2025-08-02
2025-08-01
2025-07-31
2025-07-30
2025-07-29
2025-07-28
2025-07-27
2025-07-26
2025-07-25
2025-07-24
2025-07-23
2025-07-22
2025-07-21
2025-07-20
2025-07-19
2025-07-18
2025-07-17
2025-07-16
2025-07-15
2025-07-14
2025-07-11
2025-07-10
2025-07-09
2025-07-08
2025-07-07
2025-07-06
2025-07-05
2025-07-04
2025-07-03
2025-07-02
2025-07-01
2025-06-30
2025-06-29
2025-06-28
2025-06-27
2025-06-26
2025-06-25
2025-06-24
2025-06-23
2025-06-22
2025-06-21
2025-06-20
2025-06-19
2025-06-18
2025-06-17
2025-06-16
2025-06-15
2025-06-14
2025-06-13
2025-06-12
2025-06-11
2025-06-10
2025-06-09
2025-06-08
2025-06-07
2025-06-06
2025-06-05
2025-06-04
2025-06-03
2025-06-02
2025-06-01
2025-05-31
2025-05-30
2025-05-29
2025-05-28
2025-05-27
2025-05-26
2025-05-25
2025-05-24
2025-05-23
2025-05-22
2025-05-21
2025-05-20
2025-05-19
2025-05-18
2025-05-17
2025-05-16
2025-05-15
2025-05-14
2025-05-13
2025-05-12
2025-05-11
2025-05-10
2025-05-09
2025-05-08
2025-05-07
2025-05-06
2025-05-05
2025-05-04
2025-05-03
2025-05-02
2025-05-01
2025-04-30
2025-04-29
2025-04-28
2025-04-27
2025-04-26
2025-04-25
2025-04-24
2025-04-23
2025-04-22
2025-04-20
2025-04-21
2025-04-19
2025-04-18
2025-04-17
2025-04-15
2025-04-16
2025-04-14
2025-04-13
2025-04-12
2025-04-11
2025-04-10
2025-04-09
2025-04-08
2025-04-07
2025-04-06
2025-04-05
2025-04-04
2025-04-03
2025-04-02
2025-04-01
2025-03-31
2025-03-30
2025-03-29
2025-03-28
2025-03-27
2025-03-26
2025-03-25
2025-03-24
2025-03-23
2025-03-22
2025-03-21
2025-03-20
2025-03-19
2025-03-18
2025-03-17
2025-03-16
2025-03-15
2025-03-14
2025-03-13
2025-03-12
2025-03-11
2025-03-10
2025-03-09
2025-03-08
2025-03-07
2025-03-06
2025-03-05
2025-03-04
2025-03-03
2025-03-02
2025-03-01
2025-02-28
2025-02-27
2025-02-26
2025-02-25
2025-02-24
2025-02-23
2025-02-21
2025-02-20
2025-02-19
2025-02-18
2025-02-17
2025-02-16
2025-02-15
2025-02-14
2025-02-13
2025-02-12
2025-02-11
2025-02-10
2025-02-09
2025-02-08
2025-02-07
2025-02-06
2025-02-05
2025-02-04
2025-02-03
2025-02-02
2025-02-01
2025-01-31
2025-01-30
2025-01-29
2025-01-28
2025-01-27
2025-01-26
2025-01-24
2025-01-23
2025-01-22
2025-01-21
2025-01-20
2025-01-19
2025-01-18
2025-01-17
2025-01-16
2025-01-15
2025-01-14
2025-01-13
2025-01-11
2025-01-10
2025-01-09
2025-01-08
2025-01-07
2025-01-06
2025-01-05
2025-01-04
2025-01-03
2025-01-02
2025-01-01
2024-12-31
2024-12-30
2024-12-29
2024-12-28
2024-12-27
2024-12-26
2024-12-25
2024-12-23
2024-12-21
2024-12-20
2024-12-19
2024-12-18
2024-12-17
2024-12-16
2024-12-13
2024-12-12
2024-12-09
2024-12-08
2024-12-07
2024-12-06
2024-12-05
2024-12-04
2024-12-03
2024-12-02
2024-11-30
2024-11-29
2024-11-28
2024-11-27
2024-11-26
2024-11-25
2024-11-24
2024-11-23
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/ProxmoxVE#266
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tomfrenzel on GitHub (Jan 4, 2025).
✅ Have you read and understood the above guidelines?
yes
📜 What is the name of the script you are using?
Zigbee2MQTT
📂 What was the exact command used to execute the script?
bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/zigbee2mqtt.sh)"
📝 Provide a clear and concise description of the issue.
Since the Release of Zigbee2MQTT 2.0.0 today, no Zigbee2MQTT LXCs can be created or updated.
⚙️ What settings are you using?
🖥️ Which Linux distribution are you using?
Debian 12
🔄 Steps to reproduce the issue.
Run the install script
❌ Paste the full error output (if available).
✔️ Installed Node.js
⠋Cloning into '/opt/zigbee2mqtt'...
⠦remote: Enumerating objects: 143, done.
remote: Counting objects: 100% (143/143), done.
remote: Compressing objects: 100% (139/139), done.
remote: Total 143 (delta 6), reused 76 (delta 1), pack-reused 0 (from 0)
Receiving objects: 100% (143/143), 540.96 KiB | 3.98 MiB/s, done.
Resolving deltas: 100% (6/6), done.
✔️ Set up Zigbee2MQTT Repository
npm error code EUSAGE
npm error
npm error The
npm cicommand can only install with an existing package-lock.json ornpm error npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm error later to generate a package-lock.json file, then try again.
npm error
npm error Clean install a project
npm error
npm error Usage:
npm error npm ci
npm error
npm error Options:
npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
npm error [--no-bin-links] [--no-fund] [--dry-run]
npm error [-w|--workspace [-w|--workspace ...]]
npm error [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm error
npm error aliases: clean-install, ic, install-clean, isntall-clean
npm error
npm error Run "npm help ci" for more info
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-01-03T21_45_53_474Z-debug-0.log
⠇
[ERROR] in line 45: exit code 0: while executing command $STD npm ci
🖼️ Additional context (optional).
No response
@MickLesk commented on GitHub (Jan 4, 2025):
Quickfix tomorrow
@Gugulator commented on GitHub (Jan 4, 2025):
same error.
⚙️ Using Default Settings on node pve
🖥️ Operating System: debian
🌟 Version: 12
📦 Container Type: Privileged
💾 Disk Size: 4GB
🧠 CPU Cores: 2
🛠️ RAM Size: 1024MB
🆔 Container ID: 100
🚀 Creating a Zigbee2MQTT LXC using the above default settings
✔️ Using local for Template Storage.
✔️ Using ALL for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Container 100 was successfully created.
✔️ Started LXC Container
✔️ Set up Container OS
✔️ Network Connected: 192.168.x.x
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ DNS Resolved github.com to 20.217.135.5
✔️ Updated Container OS
✔️ Installed Dependencies
✔️ Set up Node.js Repository
✔️ Installed Node.js
✔️ Set up Zigbee2MQTT Repository
⠴ Installing Zigbee2MQTT
[ERROR] in line 44: exit code 0: while executing command "$@" > /dev/null 2>&1
also tried with advanced options as non-privileged - same issue.
in addition, current version of Zigbee2MQTT LXC fails to update
@tommeh1337 commented on GitHub (Jan 4, 2025):
Same error when updating existing Zigbee2MQTT LXC.
Zigbee2MQTT doesn't start anymore after this update failure. Have to restore a backup.
@MickLesk commented on GitHub (Jan 4, 2025):
1 is enough please. We know this issue since 8 weeks
@MickLesk commented on GitHub (Jan 4, 2025):
need some testers, check PR
@daloki83 commented on GitHub (Jan 4, 2025):
Done as described, but...
@jodewee commented on GitHub (Jan 4, 2025):
Same over here
@tomfrenzel commented on GitHub (Jan 4, 2025):
@daloki83 an @jodewee you need to temporairly move the config file(s) as described over here:
https://github.com/Koenkk/zigbee2mqtt/discussions/24198#:~:text=Bare%2Dmetal%20installations
The issue is that git cannot pull the latest commits since this would ovveride your chages to the config file
@daloki83 commented on GitHub (Jan 4, 2025):
good point but then i'm running into this:
@tomfrenzel commented on GitHub (Jan 4, 2025):
Just run the update script again. Not sure why this is happening but it worked for me 👍🏽
@MickLesk commented on GitHub (Jan 4, 2025):
Yes. Update Script fix this finally. because the Update Script wont updated, and run with npm
@snippem commented on GitHub (Jan 4, 2025):
Hey, here also the same update problems to 2.0. Is it possible that you list the exact steps so that the transition to the new version goes a bit smoother?
@tomfrenzel commented on GitHub (Jan 4, 2025):
Yup makes sense. When execution the update script, it pulls the new files including the new update script which uses the pnpm command instead of the npm command. But since the old script is still running, it tries to execute the npm command after the git pull
@MickLesk commented on GitHub (Jan 4, 2025):
Look at linked PR, there are all steps
@tomfrenzel commented on GitHub (Jan 4, 2025):
@snippem The steps are listed here: #660 but before step 5 rename to configuration.yaml to configuration.yaml.bak und rename it back after the update script ran.
@daloki83 commented on GitHub (Jan 4, 2025):
@tomfrenzel @MickLesk confirmed. Update finally done
@snippem
follow:
https://github.com/community-scripts/ProxmoxVE/discussions/660
after step 4
mv your configuration.yaml and configuration.example.yaml to .bak
step 5
run the updater two times
after that mv your configuration.yaml.bak and configuration.example.yaml.bak
@JBakers commented on GitHub (Jan 4, 2025):
Confirmed working now.
Not using USB but a PoE gateway, but that doesnt change anything really regarding this.
@snippem commented on GitHub (Jan 4, 2025):
Running 2.0 now on the first instance i have of Z2M :-)
Followed the instruction and made some changes notes see:
1.) Install pnpm
npm install -g pnpm
2.) Do an Update of your config
systemctl stop zigbee2mqtt
mkdir -p /opt/z2m_backup
cp -r /opt/zigbee2mqtt/data/* /opt/z2m_backup
3.) Change Configuration of configuration yaml
nano /opt/zigbee2mqtt/data/configuration.yaml
add here in the right sections:
advanced:
homeassistant_legacy_entity_attributes: false
homeassistant_legacy_triggers: false
legacy_api: false
legacy_availability_payload: fals
device_options:
legacy: false
4.) Check if your Adapter is correct configured (i had the same issue)
nano /opt/zigbee2mqtt/data/configuration.yaml
check this part:
serial:
port: /dev/ttyACM0
adapter: zstack # <-- Add this line
ive used zstack, you can check it here: Koenkk/zigbee2mqtt#24364
Also this still works as a port:
⚙️ Determine the location of your adapter
ls -l /dev/serial/by-id
Example Output: lrwxrwxrwx 1 root root 13 Jun 19 17:30 usb-1a86_USB_Serial-if00-port0 -> ../../ttyUSB0
5.) mv your configuration.yaml and configuration.example.yaml to .bak
mv /opt/zigbee2mqtt/data/configuration.yaml /opt/zigbee2mqtt/data/configuration.yaml.bak
mv /opt/zigbee2mqtt/data/configuration.example.yaml /opt/zigbee2mqtt/data/configuration.example.yaml.bak
6.) go into main path and enter "cd"
cd /opt/zigbee2mqtt
./update.sh
run the updater two times
Note when complaining about data-backup allready avaible delete it and run update command again.
rm -r /opt/zigbee2mqtt/data-backup
run ./update.sh again
7.) Move back old configuration files.
mv /opt/zigbee2mqtt/data/configuration.yaml.bak /opt/zigbee2mqtt/data/configuration.yaml
mv /opt/zigbee2mqtt/data/configuration.example.yaml.bak /opt/zigbee2mqtt/data/configuration.example.yaml
8.) if all is correctly deployed, you can do an testrun
cd /opt/zigbee2mqtt && pnpm start
=> if it works, fine, update done
9.) Edit Service for Zigbee2MQTT
nano /etc/systemd/system/zigbee2mqtt.service
change "/usr/bin/npm start" to "/usr/bin/pnpm start" In ExecStart and start the service
systemctl daemon-reload
systemctl start zigbee2mqtt
10.) Create an App_version.txt for next updates
touch /opt/zigbee2mqtt_version.txt
nano /opt/zigbee2mqtt_version.txt
=> add 2.0.0 in file and save
The only thing i run into fornow is normally i run update in the root but i get an error:
Shutting down Zigbee2MQTT...
Generating a backup of the configuration...
Checking if any changes were made to package-lock.json...
error: pathspec 'package-lock.json' did not match any file(s) known to git
Failed to check package-lock.json.
@MickLesk commented on GitHub (Jan 4, 2025):
You need the bash of PR, its for now only in Develop Branch. Only the "update" function is against the Main Branch
@snippem commented on GitHub (Jan 4, 2025):
I don't quite understand what you mean I guess. I'm running the production version of zigbee2mqtt not the development version. Shouldn't I get the error now? Or do you mean that the manual installation of Z2M 2.00 only works now and not the standard update command? until the update script is updated to Z2M 2.00?
@MickLesk commented on GitHub (Jan 4, 2025):
Read this and execute this bash
https://github.com/community-scripts/ProxmoxVE/pull/1221
@DirkTas67 commented on GitHub (Jan 4, 2025):
Can somebody post the zigbee2mqqt.service here, I installed it today but it failed during the installation and I don't have a zigbee2mqqt.service
@MickLesk commented on GitHub (Jan 4, 2025):
how do you start zigbee2mqtt? ^^
@DirkTas67 commented on GitHub (Jan 5, 2025):
I can't start zigbee2mqtt, I just reinstalled it, the installation does not finish. I make the config file, follow the instructions from above here until I reach the edit of the .service file (and everything goes well, zigbee2mqtt starts manually) but then I can't edit the zigbee2mqtt.service file (technically I can edit it, but it is empty, since it didn't exist). So if anyone can give me the file I then can make it like it should be. Second option for me is to restore a backup from a version of august 2024 and then store it, delete the lxc, install the new one that fails to install, go thru all this stuff again and take the restored .service file. It's easier to just ask it I guess.
@MickLesk commented on GitHub (Jan 5, 2025):
Oh man...
@DittmannCz commented on GitHub (Jan 5, 2025):
Sorry if I duplicate it.
Running Z2M as LXC in PVE (bash -c "$(wget -qLO - https://github.com/tteck/Proxmox/raw/main/ct/zigbee2mqtt.sh)"
).
When I hit "update" i get this:
Acquiring necessary components...
npm error code EUSAGE
npm error
npm error The
npm cicommand can only install with an existing package-lock.json ornpm error npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm error later to generate a package-lock.json file, then try again.
npm error
npm error Clean install a project
npm error
npm error Usage:
npm error npm ci
npm error
npm error Options:
npm error [--install-strategy <hoisted|nested|shallow|linked>] [--legacy-bundling]
npm error [--global-style] [--omit <dev|optional|peer> [--omit <dev|optional|peer> ...]]
npm error [--include <prod|dev|optional|peer> [--include <prod|dev|optional|peer> ...]]
npm error [--strict-peer-deps] [--foreground-scripts] [--ignore-scripts] [--no-audit]
npm error [--no-bin-links] [--no-fund] [--dry-run]
npm error [-w|--workspace [-w|--workspace ...]]
npm error [-ws|--workspaces] [--include-workspace-root] [--install-links]
npm error
npm error aliases: clean-install, ic, install-clean, isntall-clean
npm error
npm error Run "npm help ci" for more info
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-01-05T09_49_48_569Z-debug-0.log
Failed to install necessary components.
When I start new instance from this link (https://community-scripts.github.io/ProxmoxVE/scripts?id=zigbee2mqtt) I get this.
🚀 Creating a Zigbee2MQTT LXC using the above advanced settings
✔️ Using local for Template Storage.
✔️ Using local-lvm for Container Storage.
✔️ Updated LXC Template List
✔️ LXC Container 110 was successfully created.
✔️ Started LXC Container
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
✔️ Set up Container OS
✔️ Network Connected: 192.168.11.103
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ DNS Resolved github.com to 140.82.121.4
✔️ Updated Container OS
✔️ Installed Dependencies
✔️ Set up Node.js Repository
✔️ Installed Node.js
✔️ Set up Zigbee2MQTT Repository
⠸ Installing Zigbee2MQTT
[ERROR] in line 44: exit code 0: while executing command "$@" > /dev/null 2>&1
what is recommended to proceed?
@MickLesk commented on GitHub (Jan 5, 2025):
You see the wrong Repo, right? And you see the instruction above, right?
@DittmannCz commented on GitHub (Jan 5, 2025):
clear, so shortly: how can I create new container from this proper repo when I get [ERROR] in line 44: exit code 0: while executing command "$@" > /dev/null 2>&1 ?
I know that first repo is different, thus I want new installation
@jodewee commented on GitHub (Jan 5, 2025):
Thanks, upgrade successfull !!
@sammyke007 commented on GitHub (Jan 5, 2025):
I had to edit it a little bit different:
9.) Edit Service for Zigbee2MQTT
nano /etc/systemd/system/zigbee2mqtt.service
change "/usr/bin/npm start" to "pnpm start" In ExecStart and start the service
Service wouldn't start with /usr/bin
Just FYI
@tomfrenzel commented on GitHub (Jan 5, 2025):
@MickLesk there seems to be a bug in the new install script:

The script hangs at "Setting up Zigbee2MQTT" since at some point user input is required. Typing "y" and enter makes the script proceed
@tomfrenzel commented on GitHub (Jan 5, 2025):
And the service won't start automatically and looks like something is wrong

Altrough it works when i manually start the service, it can't be enabled

@MickLesk commented on GitHub (Jan 5, 2025):
Fixed
@tomfrenzel commented on GitHub (Jan 5, 2025):
The
echo "is now gone but theWantedBy=multi-user.targetis still missing after[Install]@tomfrenzel commented on GitHub (Jan 5, 2025):
Now both are fixed 👍🏽 Thanks!
@manelrodero commented on GitHub (Jan 5, 2025):
I had seen on a Home Assistant channel that the update to version 2.0 is problematic if you don't take into account that there are changes that can break things.
According to what they explain here https://youtu.be/MBlAwQ2eBVg you have to make some changes in the configuration file.
But I have seen this whole thread about the LXC update and I'm going to wait a while to do it ;-)
At the moment, I have a question that I don't know if it has to do with the change to version 2.0 or if it was there before.
I have Zigbee2MQTT working perfectly on an unprivileged LXC and without any additional features like nesting or keyctl.
Why do you use a privileged LXC?
@82sevo commented on GitHub (Jan 5, 2025):
I'm doing a fresh install and receive this message. Am I lacking a resource?
@snippem commented on GitHub (Jan 5, 2025):
Maybe something you thought about but why not clone your existing z2m and update the cloned copy.
This is the way i do my trials 🙂
@manelrodero commented on GitHub (Jan 5, 2025):
Yes, I'm sure that when I upgrade I'll make a backup or use a clone first so as not to ruin the LXC that's running right now.
Anyway, I'm not in a hurry to upgrade because I don't think there are any major security issues (I still need to finish reading the notes for this release).
I'm more concerned about the privileged LXC issue that the script creates when doing a new installation.
@MickLesk commented on GitHub (Jan 6, 2025):
DNS issue. You cant reach Github
@MickLesk commented on GitHub (Jan 6, 2025):
Because you need an USB Passthrough. If you dont have an privileged Script, you as "normal" User cant this.
@manelrodero commented on GitHub (Jan 6, 2025):
Not entirely true.
You can pass the USB without the LXC having to be privileged.
Check out the description of my LXC:
Actually, many of the LXCs that are created by Helper Scripts could be non-privileged and we gain some security with that host isolation.
But I'm probably straying from the topic of this issue and this would lead to a more general discussion ;-)
@MickLesk commented on GitHub (Jan 6, 2025):
And this can be Done by every user? Think bigger, not only for you.
@manelrodero commented on GitHub (Jan 6, 2025):
I agree with you there. Not everyone edits configuration files.
But those who don't edit files are precisely those who don't know that a problem in a privileged LXC could affect their Proxmox host.
In that sense, I think it might be a good idea to try to make sure that LXCs have the minimum configuration necessary for their operation and that they are as secure as possible.
But as I said, I'm sorry to have strayed from the initial topic. This topic of LXC privileges would be enough for another new thread ;-)
@elad-bar commented on GitHub (Jan 7, 2025):
will join to that question about LXC being privileged,
i'm using ethernet zigbee router, i don't need the USB passthrough, why do i need to set it up as privileged?
got to this thread because the upgrade didn't work for me as well, failed on pnpm missing, fixed it locally, failed on dupliucate folder of zigbee2mqtt-2.0.0 folder, removed it and ran it again, failed on data folder is not exists (although it is),
will try installing new one and set it up from scratch, but before doing it - getting back to the question about the privileged LXC container script
thanks
@MickLesk commented on GitHub (Jan 7, 2025):
Same answer: And this can be Done by every user? Think bigger, not only for you
I close this for now, all merged and im Not answer for any Feature Request
If anyone need unprivilegeted==> use Advanced Settings