VSCode server extension installs itself on host instead on the CT

https://bugzilla.proxmox.com/show_bug.cgi?id=1042 please upgrade your pve-container package (and reboot, or apply the sysctl values manually)
Just upgraded from 2.3.9 to 2.4.0 and rebooted and now I receive the error message always, even when VSCode Extension is not connected. Basically I cannot "pct enter" anymore in any Container or run any other command! Should I upgrade to Proxmox 6.0.1 (I'm using 5.4-13)?

Code:
root@myserver:~/# sysctl -a |grep inotify
fs.inotify.max_queued_events = 16384
fs.inotify.max_user_instances = 128
fs.inotify.max_user_watches = 8192
sysctl: reading key "net.ipv6.conf.all.stable_secret"
sysctl: reading key "net.ipv6.conf.default.stable_secret"
sysctl: reading key "net.ipv6.conf.enp1s0f0.stable_secret"
sysctl: reading key "net.ipv6.conf.enp1s0f1.stable_secret"
sysctl: reading key "net.ipv6.conf.fwbr128i0.stable_secret"
sysctl: reading key "net.ipv6.conf.fwbr204i0.stable_secret"
sysctl: reading key "net.ipv6.conf.fwln128i0.stable_secret"
sysctl: reading key "net.ipv6.conf.fwln204i0.stable_secret"
sysctl: reading key "net.ipv6.conf.fwpr128p0.stable_secret"
sysctl: reading key "net.ipv6.conf.fwpr204p0.stable_secret"
sysctl: reading key "net.ipv6.conf.lo.stable_secret"
sysctl: reading key "net.ipv6.conf.veth100i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth101i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth102i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth103i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth110i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth111i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth112i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth120i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth121i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth122i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth123i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth124i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth125i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth126i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth127i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth128i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth150i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth200i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth202i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth204i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth210i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth225i0.stable_secret"
sysctl: reading key "net.ipv6.conf.veth291i0.stable_secret"
sysctl: reading key "net.ipv6.conf.vmbr0.stable_secret"
sysctl: reading key "net.ipv6.conf.vmbr1.stable_secret"
user.max_inotify_instances = 128
user.max_inotify_watches = 8192

Stopping 1 Container made the trick. It works again. Should I increase fs.inotify.max_user_instances value from 128 to 256 in /etc/sysctl.conf? Is is safe to do? Does Proxmox 6.0.1 resolve this "issue"?
 
Last edited:
pve-container in 5.x does not contain the change, you need to bump the limits manually (see the bug report).
 
  • Like
Reactions: kamzata