Search results

Thanks for the clarification. I am using the latest image to which I added said packages, so I guess I'm already good to go. As a sidenote, it seems to be working without needing to mount /sys in the container (yay, security).

Thanks for the info. I tried this with the latest Arch Linux and all seems to be working just fine. I am wondering, are there any changes that the Proxmox team made to the provided archlinux-base template? OR is it simply a LxC archlinux template from September 2019? Weirdly enough, the...

Thanks for the updates. :) I too saw that old thread and decided to play around with an updated version of the Arch Linux template, especially since the provided one in Proxmox suffers from the systemd v244.1 bug which basically breaks network setup without an extra /sys bind mount (can be...

Hi, don’t know if this was resolved, but since the underlying storage system is ZFS, lvm is most likely the issue. You should stick to ZFS datasets instead of LVM as CoW on CoW would kill your performance.

Sweet! This would greatly improve the current setup as using any newer lxc image with systemd updates requires this manual edit. So is this patch already of the testing branch? Any eta on when it will be pushed to stable? thanks a lot for the updates!

Hi, I think you meant to say that /sas was ro before that and now it will be rw. From what I can tell, you can continue to use /sys:ro and the functionality is working as expected without the risk of a writable /sys

Thanks for the details. I tried them but I cannot seem to get these two load on PVE so that the LXC container sees the and passes to Docker the requirements. Docker still says that the kernel is missing these features. :( I encountered this issue a few times before with br_netfilter and still...

With this options set, docker won't even start. Removed it as I don't think it has any impact on the Iptables rules. However, I followed the rest of the instructions step by step and it still doesn't work. It seems like there's some Lxc/Proxmox magic going on that doesn't allow docker to run...

I am unsure it has been patched/merged into the current kernel as it's still not working properly with Swarm. I'm going to guess that K8s has the same issues since it uses the same dependency...

Indeed, this is what I'm currently running (3xVMs in Swarm mode), however the extra RAM overhead is a bit too much and it would be nice to have lower overall RAM usage with Lxc since this is just for my home lab. For true production purposes I use VMs too. :)

Any updates on this from the Proxmox crew? We're at 5.3.13-2 and still doesn't seem like this has been patched. It's really awesome to have Swarm/K8s support in Proxmox, but sadly without this patch we're forced to run VMs with large overhead. :confused:

Thanks for the setup. Indeed this works just fine, I tried it now. However, now Docker Swarm doesn't seem to work regardless of what I do to convince it. The same setup above works perfectly in Docker without swarm, but as soon as I initiate Swarm, with the new interfaces it creates, iptables...

This is pretty much the same problem I have now with my setup. Swarm cannot publish ports for some reason and I couldn't make it work yet. Did you have any luck with your setup or did you just go with VMs and be done with it? Thanks!

Even with Nesting and keyctl on, I cannot seem to get Docker in LXC to properly register ports to use. It's really annoying as with LXC we can have a much smaller overhead (especially RAM usage) and being Unprivileged by default, it's great to isolate some of the docker socket issues. Did...