Search results

Hi Community, I wanted to know if anyone has ever encountered the following problem: logs: 2020-11-29T04:37:30.054129+01:00 hv18 systemd[1]: lxcfs.service: Main process exited, code=killed, status=11/SEGV 2020-11-29T04:37:30.094752+01:00 hv18 systemd[1]: lxcfs.service...

UP please.

Hi, Different mapping from different users ?

UP please

Hi Moayad,

Hi Community, I'm trying to configure my unprivileged container with id mapping (PVE 6.2). Following the documentation here : https://pve.proxmox.com/wiki/Unprivileged_LXC_containers, my container failed to start with the error below : Is there a range that we cannot map ? In my container...

Hi Stoiko, Thanks for your answer, so the only solution is to mount through the host ? Regards.

Hi Community, I don't know if it's possible but I'm trying to add an nfs mountpoint in my container via the /etc/fstab file. This one is not mounted when starting the container, if I run manually /bin/mount -a, I have the following error: mount.nfs: Operation not permitted Host server logs ...

HOST A # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # for Routing auto vmbr1 iface vmbr1 inet manual bridge_ports dummy0...

Hi Richard, Thanks for your feedback. You right, it's PREROUTING rule, my bad. * There is a container with IP 172.25.2.19 which may run alternatively at Host A or B Yes when my container A on HOST A is master, VM A have two ips 172.25.2.1 & 172.25.2.19. Then when i switch to the VM B on...

Hi Proxmox community, I'm facing an asymmetric routing issue. Each host have public and private network. Public network : vmbr0 Private network : vmbr2 Postrouting rule on HOST A : iptables -t nat -A PREROUTING -i vmbr0 -s xxxx -p tcp --dport 10636 -j DNAT --to 172.25.2.19:636 172.25.2.19...

Hi Stoiko, I've found the good formula to upgrade my VM from wheezy to stretch. The issue was effectively link to sbin folder with init scripts. The formula was to "hold" some packages like init upstart during the upgrade. Then at the end before rebooting, remove this packages and then...

Yes it's works, this is the logs after deleting folders (attached files)

when i reboot the host, folders are removed but folders are created when the container start, indeed we can't start the ct, we cant delete folders ..

I can't delete : rm: cannot remove '/sys/fs/cgroup/systemd//lxc/802/cgroup.procs': Operation not permitted rm: cannot remove '/sys/fs/cgroup/systemd//lxc/802/ns/cgroup.procs': Operation not permitted rm: cannot remove '/sys/fs/cgroup/systemd//lxc/802/ns/tasks': Operation not permitted rm...

how i can "* if it complains about the existing cgroup directory - remove that" ?

Am i forced to reboot ? I've tried to restore the dump of this CT on an other server, and when i try your command, i get : lxc-start -lDEBUG -o /tmp/8022.log -F -n 802 lxc-start: 802: tools/lxc_start.c: main: 290 No container config specified

Hi, I'm facing a similar issue but my error message is different, since i've upgraded my CT from wheezy to jessie and from jessie to stretch, my ct don't want to start. My post is here : https://forum.proxmox.com/threads/promox-5-3-1-failed-to-create-directory-sys-fs-cgroup-systemd-lxc.52864/...

You will find the logs (from journalctl) in the attached file, this is the boot sequence after rebooting my host. Logs are from the first CT.

Hi Stoiko, Thanks for your feedback, i've already try to reboot .... but it's not working.