Search results

We converted CentOS 6 OpenVZ containers a few months back to LXC via proxmox. In doing so we got everthing to work. Now cpanel recommends the following be added so crons, etc. work well: lxc.apparmor.profile: unconfined We did this on all the containers that were done but when we try to SSH...

You clear the space usually. Have you checked your nfs location for actual diskspace used aswell as your local disks on your node? one of them surely has run out of space. try loading on both servers. df -i and df -h to see.

Same thing here :) We also use nagios and this is a big problem. Cant wait either

Whenever I received that error it was always diskspace related. Either actuall disk space or inodes, etc.

https://forum.proxmox.com/threads/cannot-find-quota-file-in-lxc-centos-7-4.44601/#post-213193

Think I solved it. I thought about it a bit and I knew it worked before so it must have been some update from CentOS side. I decided to install an old version of CentOS 7 quota file. Current new version is quota-4.0.17 and I decided to install quota-4.0.14 from ...

Think I solved it. I thought about it a bit and I knew it worked before so it must have been some update from CentOS side. I decided to install an old version of CentOS 7 quota file. Current new version is quota-4.0.17 and I decided to install quota-4.0.14 from ...

How do we limit diskio with LXC containers. Lets say we have one LXC container killing the diskio constantly hence we would like to limit diskio to a good value that is just enough for all containers. Any way to perform this?

We setup new containers with centos7 template but same issue exists. CentOS 6 template seems to work perfectly. So weird

Is Ceph storage maybe CentOS 7? I notice the exact same issue with CentOS 7 all of a sudden on our containers.

looks like a reboot didnt help me. Only CentOS 7 has this issue. I know it was working before so some CentOs update must have caused this for LXC.

Did you solve this? I have the same issue

when you start the container what does "journalctl -xe" provide you with. It will usually tell you what the "real" issue is.

Not sure. But it may be related to the same issue I had awhile ago: https://forum.proxmox.com/threads/mesg-change-dev-pts-10-mode-failed-read-only-file-system.45080/#post-215115

I have the exact same issue very weird. Anyone have any ideas?

Its related to this issue that was fixed only recently: https://github.com/lxc/lxcfs/issues/13 It should appear in proxmox sometime soon :)

Hi guys Anyone run LXC Unprivileged containers with cPanel successfully? I am trying to secure our nodes better? Thanks

no ideas?

check your mounts and see if u have the same as some of us as per my temp fix https://forum.proxmox.com/threads/mesg-change-dev-pts-10-mode-failed-read-only-file-system.45080/

Fixed it doing the following: Getting closer. I ran this : mount -t devpts -o remount,gid=5,mode=620 devpts /dev/pts and now it doesnt say read only but getting new error now which made me think some stale things still left behind. So I ran find /sys/fs/cgroup/*/lxc/113* -type d | tac |...