Recent content by nobody_from_nowhere

  1. N

    Restarting a CentOS6 container makes host filesystems read-only

    with lxc-start 101 ; lxc-stop 101; lxc-start 101 I think i found the problem. I have copied directory /etc/apparmor.d from Proxmox and then i cleaned all the caches with apparmor_parser --purge-cache or simple rm -rf /var/cache/lxc/apparmor/* /var/cache/apparmor/* . Also i found i use two...
  2. N

    Restarting a CentOS6 container makes host filesystems read-only

    Yep, i unterstand, but as you can see nobody can help me include LXC team. :( So i have thought, maybe Proxmox team will want to give me a little hint how to solve the problem, how they have already solved it :) Yeah, ofc i was reading that, but on Proxmox when i create container i also use...
  3. N

    Restarting a CentOS6 container makes host filesystems read-only

    hi there, oguz ! Thx 4 ur attention! # pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve) pve-manager: 6.2-4 (running version: 6.2-4/9824574a) pve-kernel-5.4: 6.2-1 pve-kernel-helper: 6.2-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.3-pve1 criu...
  4. N

    Restarting a CentOS6 container makes host filesystems read-only

    Hi there! There is some old LXC issue https://github.com/lxc/lxd/issues/5486 (https://forum.proxmox.com/threads/problem-with-ct-dont-start-after-shutdown.54782/) , and i know you, guys from Proxmox team, somehow fix it on Proxmox. So, please, can you explain to me, how to do exactly the same on...