• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Issue Issue with Docker Container

anatol

New Pleskian
CentOS Linux 7.9.2009
Plesk Obsidian Version 18.0.35
Docker version 20.10.6, build 370c289
Docker container with MySQL 5.7.27 stopped one day ago and was not possible to start it again. Trying to start the error was:
Error: {"message":"OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting \"/var/lib/docker/containers/23385a006794b8bd06cb112d5a9c8401d6bb78370e6e7e6adea8182b2205c624/resolv.conf\" to rootfs at \"/etc/resolv.conf\" caused: mount through procfd: possibly malicious path detected -- refusing to operate on /etc/resolv.conf: unknown"}
We saved the databases from mapped folder, deleted the container, removed Docker app and reinstalled it but could not install new Docker container, the error was the same as above.
We downgrading containerd.io from 1.4.6-3.1.el7 to 1.4.4-3.1.el7 and succeeded to install a new container but there is a new issue:

We can't create a new remote database server in Plesk. All settings are the same as before, when everything worked, and it worked well since 2019.
Error: The test connection to the database server has failed because of network problems:

SQLSTATE[HY000] [2006] MySQL server has gone away
We moved temporarily the databases from mapped folder of this container to another physical server, based on Ubuntu 20.04 and the websites work now.
However on this server, based on CentOS the issue still persists.
 
Last edited:
Back
Top