Search results

this patch fixed it for me: https://forum.proxmox.com/threads/bug-in-pve-tools-df-when-adding-petabyte-scale-storage.60090/

Had the same issue, patch worked for me

and the first command was : root@proxa5:~# perl -w -e 'use Filesys::Df; use Data::Dumper; print Dumper Filesys::Df::df("/mnt/beegfs",1);' $VAR1 = { 'used' => '3092919999266816', 'bfree' => '2109416822800384', 'bavail' => '2109416822800384', 'user_blocks'...

I have exactly the same error message in the logs but i am using a BeeGFS file system as shared storage (mounted directory). Using the command "qm move_disk" it seems to copy the qcow2 or raw file from nfs to beegfs but it does not actually copy anything over and qm does not show an error...

After wrestling with permissions ( https://forum.proxmox.com/threads/cannot-change-lxc-features-nesting-nfs-as-pveadmin.49513 ) and an attempt to get unprivileged containers to work ( https://forum.proxmox.com/threads/5-3-and-unprivileged-containers-docker-works-mount-nfs-does-not.49624 ) I am...

Thanks Wolfgang, good to know. I also noticed that if you updates the features setting on multiple lxc machines it always adds another "nfs" so after 10 boxes it says nesting=1,mount=nfs;nfs;nfs;nfs;nfs;nfs;nfs;nfs;nfs;nfs. I will ask for a solution for self service in a separate post.

BTW: these are the resulting lxc confings, profiles: root@proxa1:# cat /etc/pve/lxc/333.conf #created by pct on host proxa1 arch: amd64 cores: 2 features: keyctl=1,nesting=1,mount=nfs;nfs4 hostname: tstunpr1 memory: 512 net0: name=eth0,bridge=vmbr0,hwaddr=72:22:FD:E1:95:B8,ip=dhcp,type=veth...

I upgraded from 5.2 to 5.3 and am trying to re-deploy self service unprivileged containers where users create an LXC container and then can do whatever they need to do (mostly installing docker, mounting file systems etc) First I am disabling all the magic hacks that were required to run docker...

Just saw here that only root can change feature flagf https://forum.proxmox.com/threads/lxc-apparmor-denied.49290/#post-230574 So how I then globally enable container besting and nfs ?

I give users the role PVEAdmin for their pool to do self service. Now that there are Features for container nesting and nfs I would like to allow them change that. Unfortunatelty the PVE admin role does not seem to have permissions to change this. Is there a way to enable this globally ? I used...

It ‘s the final step when creating a new container through the web ui

I got the same issue with the very latest proxmox 5 (updated today) Can't call method "map_method_by_name" on an undefined value at /usr/share/perl5 PVE/RESTHandler.pm line 299. (500) I am using some python code to create users, pools, acls and groups. users get the role PVEAdmin and...

I have had this problem for a while: corosync stops syncing and pvecm looses quorum i "fixed" this by running this cron job every few minutes. this allows corosync to to resync for a while but when I connect via web ui only the current node seems online...

well, it turns out that the 'ifconfig' binary is curiously missing from the current 18.04, used these steps to fix: - create new tree rootfs-cp and put old ifconfig into rootfs-cp/sbin - patch /uar/bin/dab so rootfs-cp tree is copied to rootfs before bootstrap + use File::NCopy...

after I install lxc 2.0.9 from source it bombs out right away ... rolling back. unpack: liblz4-1 command 'lxc-attach -n 55b6fb1f-b556-4e33-a4b2-c168b8ed98d6 --rcfile /root/proxmox-templates/ubuntu-18.04/config --clear-env -- defenv dpkg --force-depends --unpack...

I should add: lxc-attach --version 2.0.7

I wanted to start testing Ubuntu 18.04 Alpha and tried patching /usr/share/perl5/PVE/DAB.pm by adding configs for suite bionic where I found xenial grep xenial /usr/share/perl5/PVE/DAB.pm } elsif ($suite eq 'xenial') { $suite eq 'xenial' || $suite eq 'wily' || $suite eq 'vivid' ||...

+1 for CRIU. For us most situations is for a production workload and if we have to take downtime that is not popular. LXC is a key benefit of proxmox, there are many other KVM solutions so it would be good if proxmox would concentrate more on its strengths

I was wondering what the status of this feature is. I see in the roadmap at https://pve.proxmox.com/wiki/Roadmap * live migration with local storage (qemu) but I do not see LXC live migration. Is CRIU no longer planned or can it be added to the road map ?

if anyone finds this useful: This tool allows you to deploy and manage many LXC containers very quickly. It requires a mechanism for dynamic dns with your virtual appliance. https://pypi.python.org/pypi/proxmox-tools issue tracker: https://github.com/FredHutch/proxmox-tools/issues