Ah, right. Sorry. Yes, I'm root, but I was using a different user for creating the container and that didn't work.
I'll try again using root credentials, see whether that works. Ansible is using the REST api, that shouldn't make a difference though, right?
Do you have any documentation on what exactly the numbers mean, and which units are used. E.g, for cpu I get a value like: 0.00149740172862036 , but I have no idea what that refers to, and whether it has anything to do with the total amount of cpus a container has for example.
Thanks!
Would it be possible to specify a few 'allowed' root folders where this mounting is allowed via the API? I'm using ansible to create and manage lxc containers, and being able to manage my storage like that would be a huge help. My current options are some whacky/hacky crap like using ansible to...
I'm running into the same issue. Did you figure out what's causing it? It's fairly hard to debug, since some restarts actually seem to work, but then next one hang again at the network interfaces stage. For me it happens also with newly created containers (using PVE 4.3 at the moment).
Ok, figured it out. It was the kernel ( pve-kernel-4.4.13-2-pve ). Booting with the old one ( pve-kernel-4.4.6-1-pve ) works. Any idea what could have changed in regards to nfs?
I've installed Proxmox ontop of Debian Jessie the other day, and run into a problem with nfs-mounting a folder onto the host system (not lxc). I wouldn't be able to 'ls' or 'cd' into a subdirectory of the root mount folder (the root itself was fine) as a user, was getting an error like:
ls...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.