Hi there,
we just bought a Synology RS-815+ that I want to use as storage for our Proxmox server. The RS-815+ is connected via NFS.
For testing purposes I created a new CentOS container on the new storage using "centos-7-x86_64-minimal.tar.gz" from https://openvz.org/Download/template/precreated
A "yum update" is going to update this container to CentOS 7.1, but the update fails with the following error:
If I create the same container on the local storage and do the update there, it works just fine - so the error seems to be related to NFS?
Is there anything I could have done wrong with the NFS configuration on the Synology device that would cause this error?
Edit: I found this on https://bugzilla.redhat.com/show_bug.cgi?id=648654 (Comment 13):
If NFS does not support file capabilities (I don't know if that's a fact) how would we be able to run a linux container with Proxmox on a NFS storage device???
Any ideas?
Thanks for any help!
Ralph
we just bought a Synology RS-815+ that I want to use as storage for our Proxmox server. The RS-815+ is connected via NFS.
For testing purposes I created a new CentOS container on the new storage using "centos-7-x86_64-minimal.tar.gz" from https://openvz.org/Download/template/precreated
A "yum update" is going to update this container to CentOS 7.1, but the update fails with the following error:
Code:
Running transaction
Updating : systemd-208-20.el7_1.2.x86_64 1/2
Error unpacking rpm package systemd-208-20.el7_1.2.x86_64
error: unpacking of archive failed on file /usr/bin/systemd-detect-virt: cpio: [b]cap_set_file[/b]
Verifying : systemd-208-20.el7_1.2.x86_64 1/2
systemd-208-11.el7_0.5.x86_64 was supposed to be removed but is not!
Verifying : systemd-208-11.el7_0.5.x86_64 2/2
Failed:
systemd.x86_64 0:208-11.el7_0.5 systemd.x86_64 0:208-20.el7_1.2
If I create the same container on the local storage and do the update there, it works just fine - so the error seems to be related to NFS?
Is there anything I could have done wrong with the NFS configuration on the Synology device that would cause this error?
Edit: I found this on https://bugzilla.redhat.com/show_bug.cgi?id=648654 (Comment 13):
I guess we should also question why NFS does not support file capabilities
If NFS does not support file capabilities (I don't know if that's a fact) how would we be able to run a linux container with Proxmox on a NFS storage device???
Any ideas?
Thanks for any help!
Code:
proxmox-ve-2.6.32: 3.4-150 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-3 (running version: 3.4-3/2fc72fee)
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-34-pve: 2.6.32-140
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.4-3
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-32
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
Ralph
Last edited: