09-26-2020, 04:47 AM
(09-25-2020, 11:46 PM)fitkoh Wrote: So I guess what I'm wondering is if anyone has any experience in hacking a workaround in docker to make it work on openVZ? Some experience that will actually work? Or is this a hopeless endevour, and I should just close the service and ask for a refund. I've had this vps less than 2 days, and they have a full 7 day refund policy, so it's no issue to ask for a refund. I just want to make sure I explore all the options before I do.The idea of running a Docker engine inside an OpenVZ guest system is just insane!... and would/should never work!!
(09-25-2020, 11:46 PM)fitkoh Wrote: Eventually, what I figured out, is that the vps uses kernel 4.15.0 which does not support cgroups. Cgroups is necessary for docker to provision resources for and keep contained the services it runs. Docker itself will run, and the "hello world" docker runs with no issue, but docker fails at deploying the nginx proxy used to direct traffic between the containers.And No!.. the problem is not Cgroups' support in your case, because CGroups are supported starting in Linux kernel 3.10; it's CGroups v2 that are implemented in kernel 4.15. And Docker engine requires CGroups v1 (v2 is still not supported by Docker last time I checked) for its process isolation for the containers it runs.
Why the idea of Docker on OpenVZ is insane?.. Your OVZ VPS uses the host kernel and I don't think it has the permissions required to use CGroup features which are responsible for managing and monitoring resource allocation for processes under its control by setting their resource limits ( CPU, memory etc..) Nor does it have permission for the kernel namespacing feature that is also a must for Docker and on and on...
Better get a KVM VPS and then running Docker will be possible if the VPS has enough resources to handle its tasks.
Good luck!