Cannot create LXC Container in Proxmox 4

[fkh]

Hi guys

I just set up a couple of new host machines with Proxmox 4. Now I am not able to create LXC containers on those hosts. During the creation of the LXC container the following error occurs (in the GUI dialog at the end):

command '/usr/bin/file -b -L /var/lib/lxc/100/rootfs/usr/bin/file' failed: open3: exec of /usr/bin/file -b -L /var/lib/lxc/100/rootfs/usr/bin/file failed at /usr/share/perl5/PVE/Tools.pm line 376

After that when trying to start the container it doesn't work. This happens on two hosts that both have been set up in the last couple of days. KVM works though. I pasted the output of the shell commands at pastebin.

http://pastebin.com/r0g7UR8D

Does anyone have an idea of what is going wrong here. I've set up a couple of other machines the same way like those two a couple of weeks ago and those were working just fine.

Cheers
fkh

 

[dietmar]

what template do you use? Inside the template, there should be a file called "/usr/bin/file" - we use that to detect the architecture type.

 

[fkh]

Hi Dietmar

Thank you very much for the fast reply. I am using the templates that are available via the Proxmox web ui (http://download.proxmox.com/images/system/debian-8.0-standard_8.0-1_amd64.tar.gz).. I also tried the Ubuntu 15.04 image (http://download.proxmox.com/images/system/ubuntu-15.04-standard_15.04-1_amd64.tar.gz) and I also deleted them and downloaded them again but the problem remains the same.

I also executed pveam update before downloading the LXC templates for the second time but that didn't help either.

Any help is much appreciated.

Cheers
fkh

Edit: I forgot to mention that I've checked the Debian template file and it has in fact a file availble at usr/bin/file (SHA1 = 1d31de3fbfc7b5f6b45e467f979d79f3ab64b356, MD5 = 11688e2c00ac15c25da712ec74994627, file size 19064 bytes).

 

[dietmar]

what is the output of

# pveversion -v

is this a standard installation using the Proxmox CD?

 

[fkh]

Hi Dietmar

It's a plain Debian (OVH image) and on top of it I've installed Proxmox 4 as described at https://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Jessie.

The output of pveversion -v is:

root@host4 ~ # pveversion -v
proxmox-ve: 4.0-16 (running kernel: 4.2.2-1-pve)
pve-manager: 4.0-50 (running version: 4.0-50/d3a6b7e5)
pve-kernel-4.2.2-1-pve: 4.2.2-16
lvm2: 2.02.116-pve1
corosync-pve: 2.3.5-1
libqb0: 0.17.2-1
pve-cluster: 4.0-23
qemu-server: 4.0-31
pve-firmware: 1.1-7
libpve-common-perl: 4.0-32
libpve-access-control: 4.0-9
libpve-storage-perl: 4.0-27
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-10
pve-container: 1.0-10
pve-firewall: 2.0-12
pve-ha-manager: 1.0-10
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.3-1
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2
criu: 1.6.0-1

Thank you very much for your help.
fkh

 

[dietmar]

I am unable to reproduce that here.

 

[fkh]

Hi Dietmar

Thank you very much for your help anyway. Guess I will try to reinstall Proxmox on those servers and hope that the problem doesn't occur anymore.

Cheers and have a nice weekend
fkh

 

[fkh]

In case anyone is having the same issue the following might be useful.

The issue seems to be related to the current OVH Debian 8 image. I could reproduce this on three different dedicated servers at OVH and all had the same issue (described in the first post of this thread). On the other hand when using a regular Debian iso on a local server everything was working just fine. I got it working now by using the old Debian 7 image and upgrading it to Debian 8 afterwards. Then I installed Proxmox and it's working now as expected. I didn't check the pre-build Proxmox 4 image from OVH though.

This was surprising since I installed other Proxmox hosts about two weeks ago (using the Debian 8 image) and back then everything was working well. Anyway I just thought I share this information in case somebody else might have such issues.

 

[manu]

@fhk:

Could it be that the "file" command is missing on your host ?
If anyone has acess to a fresh new OVH Debian8 host, what is the output of this ?
dpkg -l file

Btw any reasons not to use the Proxmox images in OVH ? We checked ourselves that they're correct, so you would spare you the trouble ...

 

[farstars]

Hi everyone,

I just ran into the same issue on a new Debian 8 host at OVH.

The file command indeed seems to be missing:
file
-bash: file: command not found

Luckily a simple
apt-get install file
solved the issue.

Maybe that helps any fellow sufferers.

 

[manu]

The package "file" has priority standard so it should be part of a standard Debian installation.
You can verify this with:

aptitude search ~pstandard ~prequired ~pimportant -F%p | grep ^file

Now it seems OVH proposes a Debian image which is not installing the standard recommend packages from Debian.

Maybe we can a depedency to pve-container to the file package, but it would be better if OVH fixed their image IMHO.

 

[manu]

And thanks for bringing this issue up.