CentOS 8.1 LXC unsupported centos release

M

mhaluska

Well-Known Member
Sep 23, 2018
53
6
48
Hi, please fix version for CentOS 8.1 in /usr/share/perl5/PVE/LXC/Setup/CentOS.pm

Bash: 
# pveversion
pve-manager/6.1-5/9bf06119 (running kernel: 5.3.13-1-pve)

Code: 
lxc-start 320 20200116195154.278 INFO     conf - conf.c:run_script_argv:372 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "320", config section "lxc"
lxc-start 320 20200116195155.337 DEBUG    conf - conf.c:run_buffer:340 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 320 lxc pre-start produced output: unsupported centos release 'CentOS Linux release 8.1.1911 (Core) '

lxc-start 320 20200116195155.357 ERROR    conf - conf.c:run_buffer:352 - Script exited with status 25
lxc-start 320 20200116195155.357 ERROR    start - start.c:lxc_init:897 - Failed to run lxc.hook.pre-start for container "320"
lxc-start 320 20200116195155.358 ERROR    start - start.c:__lxc_start:2032 - Failed to initialize container "320"

Fix:
Code: 
# diff CentOS.pm.old CentOS.pm
23c23
<       if ($1 >= 5 && $1 <= 8) {
---
>       if ($1 >= 5 && $1 <= 8.1) {
 
  • Like
Reactions: Jaime Hablutzel and anonion
Hi

UP please. Having same issue.


Code: 
lxc-start 103 20200117012001.592 INFO     conf - conf.c:run_script_argv:372 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "103", config section "lxc"
lxc-start 103 20200117012001.926 DEBUG    conf - conf.c:run_buffer:340 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 103 lxc pre-start produced output: unsupported centos release 'CentOS Linux release 8.1.1911 (Core) '

lxc-start 103 20200117012001.935 ERROR    conf - conf.c:run_buffer:352 - Script exited with status 25
lxc-start 103 20200117012001.935 ERROR    start - start.c:lxc_init:897 - Failed to run lxc.hook.pre-start for container "103"
lxc-start 103 20200117012001.935 ERROR    start - start.c:__lxc_start:2032 - Failed to initialize container "103"

Thanks
 
+1. Same issue

Code: 
lxc-start 121 20200117044254.560 INFO     conf - conf.c:run_script_argv:356 - Executing script "/usr/share/lxc/hooks/lxc-pve-prestart-hook" for container "121", config section "lxc"
lxc-start 121 20200117044255.140 DEBUG    conf - conf.c:run_buffer:326 - Script exec /usr/share/lxc/hooks/lxc-pve-prestart-hook 121 lxc pre-start with output: unsupported centos release 'CentOS Linux release 8.1.1911 (Core) '

lxc-start 121 20200117044255.146 ERROR    conf - conf.c:run_buffer:335 - Script exited with status 25
lxc-start 121 20200117044255.146 ERROR    start - start.c:lxc_init:861 - Failed to run lxc.hook.pre-start for container "121"
lxc-start 121 20200117044255.146 ERROR    start - start.c:__lxc_start:1944 - Failed to initialize container "121"
lxc-start 121 20200117044255.146 ERROR    lxc_start - tools/lxc_start.c:main:330 - The container failed to start
 
KatyComputer said:
Please encourage your clients and organizations to become Proxmox subscribers so more developers can be hired to implement latest & greatest technologies.
Click to expand...

Just like most other users, I use proxmox for personal use as a Home Server.
I'm not totally against subscribing to support... but at the moment I'm not yet convinced to stay on proxmox.
Indeed, the first VM I'm building, a Windows with GPU passthrough, Proxmox Freeze because its Kernel is not able to handle the D3 State of the PCI slots.
Second VM I'm building, a simple OS update leads to the error present in this topic.
And before I could create VMs, I fought to get a stable Proxmox using RAID (so ZFS) because the basic configuration caused problems (I forgot the details).
Anyway, I think I'll wait and see how my experience with the tool evolves before signing for at least 1 year of collaboration... :rolleyes:


Regarding this topic, the issue can be solved as explained by first OP editing file :

nano /usr/share/perl5/PVE/LXC/Setup/CentOS.pm

with

Code: 
if ($1 >= 5 && $1 <= 8.1) {

instead of

if ($1 >= 5 && $1 <= 8) {

(maybe a wildcard can also be used ? 8* ?)

If someone can push that edit into proxmox Git it could be nice for other users...
 
Last edited:
KatyComputer said:
Please encourage your clients and organizations to become Proxmox subscribers so more developers can be hired to implement latest & greatest technologies.
Click to expand...

Same as above comment. I'm using Proxmox for home virtualization. Anyway, it should be no problem to support you with community license, but I've two small systems and one laptop for quorum, so it's 3 licenses, around a half of current price of my hardware, this is little but too much for me.
My Employer is really big company, so everything on VMware or mainframe, I've less then zero power here.
 
Makes sense to me - that's why I suggested a multi-system deal, we have a number of clients with 2 or three staff members, I would like to put them all on Community licenses, but it's not prudent for these small firms to spend the $100 for community licenses.

OTOH, I like to remind the community that it benefits us all if we show the Proxmox team a bit of love with subscription revenue.
 
But without community license I'm also useful to Proxmox when reporting issue like this (this was just small) with fix.
Think about some Proxmox beginner will discover this issue, report it here asking for help. So I saved some Proxmox stuff time = money ;)
 
You must log in or register to reply here.
Top Bottom