I can't login into centos 7 when I use official template.

[SmithCruise]

I use official container template to create a VM. And I set the password is 123456, but I can't login into system. It told me that Login incorrect.

The template I used is : centos-7-default_20190926_amd64.tar.xz

And another question, when I use images from https://uk.images.linuxcontainers.org/ . I can't create a VM (TASK ERROR: unable to create CT 104 - unsupported centos release 'CentOS Linux release 8.0.1905 (Core) ') , what shoud I do if I want to use images from this website.

 

[wolfgang]

Hi,

this original Proxmox VE works here without problems.
do you have any special LANG settings?

What Proxmox VE version do you use?

pveversion -v

 

[SmithCruise]

Hi,

this original Proxmox VE works here without problems.
do you have any special LANG settings?

What Proxmox VE version do you use?

pveversion -v

proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)

 

[Mike Lupe]

I use official container template to create a VM. And I set the password is 123456, but I can't login into system. It told me that Login incorrect.

The template I used is : centos-7-default_20190926_amd64.tar.xz

I had a similar case some time ago - I couldn't login to the 20190926 version (no keyboard issue), so I had to use the older version from 2017, which worked as always. Strangely, after a totally unrelated reboot of all cluster nodes and later on a retry to download and use the 20190926 version, it suddenly worked as intended. Maybe I updated to a recent PVE prior to rebooting the nodes, I really can't remember.

 

[SmithCruise]

I had a similar case some time ago - I couldn't login to the 20190926 version (no keyboard issue), so I had to use the older version from 2017, which worked as always. Strangely, after a totally unrelated reboot of all cluster nodes and later on a retry to download and use the 20190926 version, it suddenly worked as intended. Maybe I updated to a recent PVE prior to rebooting the nodes, I really can't remember.

Yeah, I update PVE recently too. Let me have a try.

 

[firmonion]

Did this ever get resolved? I too am having this issue with the latest official centos 8 container template.
Here's my output for pveversion -v

Spoiler

proxmox-ve: 5.4-2 (running kernel: 4.15.18-21-pve)
pve-manager: 5.4-13 (running version: 5.4-13/aee6f0ec)
pve-kernel-4.15: 5.4-9
pve-kernel-4.15.18-21-pve: 4.15.18-48
pve-kernel-4.15.18-20-pve: 4.15.18-46
pve-kernel-4.15.18-15-pve: 4.15.18-40
pve-kernel-4.15.18-14-pve: 4.15.18-39
pve-kernel-4.15.18-10-pve: 4.15.18-32
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-12
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-55
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-14
libpve-storage-perl: 5.0-44
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-7
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
proxmox-widget-toolkit: 1.0-28
pve-cluster: 5.0-38
pve-container: 2.0-40
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-22
pve-firmware: 2.0-7
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 3.0.1-4
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-54
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2

Edit: Noticed that I'm running a dated version of Proxmox, from further research that seems to be the issue. Following the upgrade guide here.