• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Issue Clicking on Docker container causes memory exhaustion

speedbird

Basic Pleskian
I currently run into an issue with Docker on my server.

For a friend of mine, I run a docker image containing a java server. However for some days now, whenever I click on the docker "machine" in Plesk or on the "protocols" button I don't see anything at all. Instead, my computer obviously starts downloading something huge from the server until there's a Plesk error message with something like "tried to allocate xxxxxxxxxxxxx bytes" and so on.

I am not able to see console output of the docker image anymore. What's going on here? Is there some kind of massive log file playing nuts here or what's going on?

Any ideas on how to get this thing responsive again?

Thanks!
 
Back
Top