ATTEMPTING Docker on 256MB OpenVZ. What could go wrong. Let me list: cgroup escape, kernel exploit, container breakout, host compromise, your keys stolen, your cat photos ransomw! fail2ban won't save you here. iptables won't save you. The provider—let us not name names—runs kernel 3.10. WHAT YEAR IS THIS. I warned you.
256MB OpenVZ for Docker—am I the clown here?
airgapped, encrypted, faraday'd, still worried
I ran Docker 20.10 on 512MB OpenVZ at GreenCloudVPS Tokyo without issue. 256MB seems difficult. Perhaps consider Podman rootless, or static binaries without container runtime. Asia-Pacific locations often offer better price-memory ratios if relocation is possible.
conbini > datacenter snacks
kenji3 said:
256MB seems difficult
Can be done one, but must go slow-slow. My friend at HostHatch Singapore have 256MB also, can run docker with some tikungan. Thank you for the suggestion podman, but the cgroup v1 problem same same. Wkwkwk.
docker --storage-driver=vfswill eat eat eat the RAM, not recommend. Thank you.
wrap it, ship it, pray it