Recent content by seneca214

For any others that may run into this. We believe we've found a solution that allows for both CentOS 7 and Rocky 8 containers on the same Proxmox host. For Rocky 8 containers add the following line to the /etc/pve/lcx/ID.conf file: lxc.mount.auto = cgroup:rw:force We found this hint from the...

We believe the underlying issue here is the change made to allow CentOS 7 containers to work with Proxmox 7 or greater: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_security_considerations. Specifically, adding this kernel boot argument 'systemd.unified_cgroup_hierarchy=0' to the...

Hello, Looking for help troubleshooting an issue we've come across with Proxmox 7.2 - 7.4 hosts and Rocky OS 8 containers. The container will start and run normally, however, and this can be intermittent, when a systemctl command is used, such as systemctl start <service> the systemctl hangs...

When the kworker issue is present we do see the web console show grey icons on all containers. This does sound like the same issue.

So far, we've been unable to reproduce the issue with any server that's been rebooted with the firewall rules in place. If nothing else, this seems to greatly mitigate the issue.

Sharing this possible workaround posted on a related thread in case it helps others out: https://forum.proxmox.com/threads/lxc-container-reboot-fails-lxc-becomes-unusable.41264/ Proxmox's support unfortunately hasn't been any help with this. We've been trying to at least find a workaround on...

@weehooey on our test server, we've installed the iptables-persistent package. This keeps a file in /etc/iptables/rules.v6 that automatically loads on boot.

@weehooey 1) That's great to hear. Let's hope others can help test and confirm. 2) This was a change we've only tested today and have been running them manually. I'll get back to you on how we set it up to persist across reboots assuming this does indeed work until Proxmox comes out with...

/etc/network/ip6tables.up.rules contains: *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT DROP [1:56] COMMIT After applying, running ip6tables -L shows: Chain INPUT (policy DROP) target prot opt source destination Chain FORWARD (policy DROP) target prot...

Proxmox's support unfortunately hasn't been any help with this. We've been trying to at least find a workaround on our Proxmox servers. Simply as a test, referencing this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765980, we setup ip6tables on one of our nodes to block all...

You may be running into the same issue reported in these bug reports and posts: https://bugzilla.proxmox.com/show_bug.cgi?id=1943 https://forum.proxmox.com/threads/lxc-restart-creates-kworker-cpu-100.40934/...

We're experiencing this same issue with various Proxmox v5.3 servers and have paid Proxmox support that hasn't been able to provide a solution for us. What is the solution here since this post is marked as solved?

Hello, On our Proxmox 4.4 server we're unable to start containers, receiving the following error: TASK ERROR: command 'systemctl start lxc@<ID>' failed: exit code 1 These are CentOS 7 containers. # systemctl status lxc@100.service ● lxc@100.service - LXC Container: 100 Loaded: loaded...

Hello, If it is a problem with virt-what, its only in regards to OpenVZ -> LXC migrated VMs. virt-what works fine with other CentOS physicial servers, KVM VMs and LXC VMs that weren't migrated.

Thank you. Anyone else notice virt-what not working with Proxmox with converted/migrated OpenVZ->LXC containers?