• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

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