• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Docker Incompatible with Cloudlinux

Hex

Regular Pleskian
Plesk Certified Professional
TITLE:
Docker Incompatible with Cloudlinux​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
CloudLinux 7.6
Product Plesk Onyx
Version 17.8.11 Update #47
​
PROBLEM DESCRIPTION:
Unable to deal with docker after converting to Cloudlinux so the docker is useless with Cloudlinux and this is not mentioned in Software Requirements for Plesk​
STEPS TO REPRODUCE:
1-Install Plesk
2-Convert to Cloudlinux
3-Run any container​
ACTUAL RESULT:
Error: {"message":"cgroups: cannot find cgroup mount destination: unknown"}​
EXPECTED RESULT:
Container Created and Started.​
ANY ADDITIONAL INFORMATION:
Another error message when you start a previously deployed containers after converting to Cloudlinux 7.6

Error: {"message":"OCI runtime create failed: container with id exists: b8bb303d1513a5f294672129a46fd8520aed5fe7621267c5359f68ccd41cb27c: unknown"}
​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 
Last edited:
Using Docker

Docker is supported in Plesk for the following operating systems: CentOS 7, RedHat 7, Debian 8, Debian 9, Ubuntu 14.04, and Ubuntu 16.04.

Indeed, Docker Incompatible with CloudLinux .
 
Mark, Thank you for your input here, the problem with this is that I can't use it with CentOS yum package manager, Do you have a workaround?

Actually It will be a good idea to use a remote docker node connected to Plesk.

I tried to use the second node with docker installed on CentOS7 but I'm facing a communication issue with the node from Plesk, I followed this instruction step by step twice and downloaded all *.pem files to corresponding fields in Plesk and with some errors like : connection refused, connection timeout , no route. so I couldn't get to use this method. I also tried the none SSL port 2375 and disabled all kind of firewall and still getting refused.

But I think it will be more complicated setup and some update will break the building.

Any ideas much appreciated.
 
Back
Top