Hmmm, nevermind, I see this same tmpfs behaviour in CentOS 7 and Debian containers too. None the less, I am having OOM problems with this container as discussed in the linked linuxcontainers.org thread. Here's one where systemd-journal was killed:
Dec 16 14:10:49 HOST kernel: dnf invoked...
Just to bump this thread, I upgraded from Proxmox 5 to Proxmox 6 and this issue still persists. I still need the socat workaround to get the internal certificate generator to work.
My /etc/gai.conf is stock, with everything commented out.
My /etc/hosts looks like this, with relevant info...
I'm seeing this issue in a CentOS 8 container too. For me it's manifesting in the tmpfs mounts getting sized as half of the host memory, rather than half of the memory of the guest (the host has 32GB, the guest is set up with 256mb).
# df -h
Filesystem Size Used Avail Use%...
I just made a simple systemd unit to keep socat running:
cat /etc/systemd/system/pve-ipv6-cert-proxy.service
[Unit]
Description=Forward IPv6 port 80 to proxomox acme validation server
[Service]
ExecStart=/usr/bin/socat TCP6-LISTEN:80,fork,ipv6only=1,reuseaddr TCP4:127.0.0.1:80
[Install]...
I see there's a bug open for this https://bugzilla.proxmox.com/show_bug.cgi?id=2061 and that there are even some recent commits that look to be getting this implemented, but I needed to get this working now, so as a workaround, I set up a quick socat listener to forward connections from IPv6 to...
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.