5 ms·
For those who a) use Proxmox to b) manage containers c) some of which are of ostype: unmanaged (e.g. those who run a virtual OpenWRT router, like me...) be warn
by the_third_wave 5y ago
For those who a) use Proxmox to b) manage containers c) some of which are of ostype: unmanaged (e.g. those who run a virtual OpenWRT router, like me...) be warned that the current version of Proxmox will not start those containers due to a bug/an omission in the PVE::LXC::Setup package (/usr/share/perl5/PVE/LXC/Setup.pm) which makes it attempt to call a non-existing method to configure cgroupv2 support on such containers. The following patch will work for now while the problem has not yet been solved in the repo:
--- /usr/share/perl5/PVE/LXC/Setup.pm.org
+++ /usr/share/perl5/PVE/LXC/Setup.pm
@@ -424,6 +424,8 @@
sub unified_cgroupv2_support {
my ($self) = @_;
+ $self->{plugin} //='PVE::LXC::Setup::Base'; # unmanaged
+
$self->protected_call(sub {
$self->{plugin}->unified_cgroupv2_support();
});
I hit upon this snag when updating the server-under-the-stairs which went off without any problems except for the router container not starting.
- cridenour 5y agoThanks for the heads up! I’ll wait for the .1 release to avoid messing up videos for my bossy toddlers.