Im currently running the beta version and decided to upgrade one of my old containers and i guess i went version to far untill Ubuntu 17.04. and now it just stubbornly gives me the error "unsupported Ubuntu version '17.04'" and refuse to start. can i get around this somehow without restoring from a backup?
[SOLVED] unsupported Ubuntu version '17.04'
- Thread starter zimzim
- Start date
Im not sure to what version you are refering?
Im running the latest beta to my knowledge.
Or something else i should update?
//kim
Im running the latest beta to my knowledge.
Code:
pveversion -v
proxmox-ve: 5.0-9 (running kernel: 4.10.11-1-pve)
pve-manager: 5.0-10 (running version: 5.0-10/0d270679)
pve-kernel-4.2.6-1-pve: 4.2.6-26
pve-kernel-4.10.8-1-pve: 4.10.8-7
pve-kernel-4.10.11-1-pve: 4.10.11-9
libpve-http-server-perl: 2.0-4
lvm2: 2.02.168-pve2
corosync: 2.4.2-pve2
libqb0: 1.0.1-1
pve-cluster: 5.0-7
qemu-server: 5.0-4
pve-firmware: 2.0-2
libpve-common-perl: 5.0-12
libpve-guest-common-perl: 2.0-1
libpve-access-control: 5.0-4
libpve-storage-perl: 5.0-3
pve-libspice-server1: 0.12.8-3
vncterm: 1.4-1
pve-docs: 5.0-1
pve-qemu-kvm: 2.9.0-1
pve-container: 2.0-6
pve-firewall: 3.0-1
pve-ha-manager: 2.0-1
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-1
lxcfs: 2.0.7-pve1
criu: 2.11.1-1~bpo90
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.9-pve16~bpo90Or something else i should update?
//kim
this was added in pve-container 2.0-8, which is not yet publicly available except in git: https://git.proxmox.com/?p=pve-container.git;a=commitdiff;h=d9d448faebe311d4fd88201abcdf4ce9f2edd393
there's currently a rather big change set "in flight" which is affecting several repositories, which is why other smaller changes like this have not yet been released in package form. this should change soon you can set a container's ostype to "unmanaged" as a workaround, but this will skip all the OS-dependent modifications and setup operations PVE usually does.
you can set a container's ostype to "unmanaged" as a workaround, but this will skip all the OS-dependent modifications and setup operations PVE usually does.
set "ostype" to "unmanaged" in the container configuration. you cannot set it to force a certain version, as the version is always detected. but you could temporarily camouflage your container as 16.10 by editing the /etc/lsb-release file inside the container and modifying the DISTRIB_RELEASE line. once pve-container 2.0-8 is installed on your system, revert the change again.