• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Issue Rollback docker extension

zed2007

Basic Pleskian
Server operating system version
CentOS 7.9
Plesk version and microupdate number
Version 18.0.57 Update #5
Hi to all. Since docker version 25.0.0. I can't use docker because of a problem with the storage driver. Before version 25.0.0 everything worked great. Is it possible to roll back to a previous version?
Thanks in advance.
 

Attachments

  • DR_Error.png
    DR_Error.png
    63.1 KB · Views: 5
Righ now, I have same problem

This weeknd docker was upgraded in almalinux 8.9 and not start any more, a lot of logs say have conflicts in with firewalld and docker0 interface, not changes if disable firewall.

Code:
ERROR: ZONE_CONFLICT: 'docker0' already bound to a zone

I try remove docker0 from plesk, but not posible because say network manager own docker0 and is in use :/

In my case, I roll back upgrade ( not know if works in centos 7 )

Code:
yum history

In my case history show UID 85 without any information just 5 packeges changed.

Code:
yum hisotry info 85

Show me docker upgrade:

Code:
ID de transacción: 85
Hora inicial     : sáb 20 ene 2024 03:35:41 CET
Rpmdb inicial    : 1252:22b0c39de2e73e33be96ae2581dc4908d2cb5381
Hora final       : sáb 20 ene 2024 03:35:56 CET (15 segundos)
Rpmdb final      : 1252:f2b527092485ef4971739b5d6c5ad7da4dfbdebf
Usuario          : Sistema <no definido>
Código de retorno: Éxito
Publicación      : 8
Línea de comando :
Comentario       :
Paquetes modificados:
    Upgrade  docker-buildx-plugin-0.12.1-1.el8.x86_64      @plesk-ext-docker
    Upgraded docker-buildx-plugin-0.11.2-1.el8.x86_64      @@System
    Upgrade  docker-ce-3:25.0.0-1.el8.x86_64               @plesk-ext-docker
    Upgraded docker-ce-3:24.0.7-1.el8.x86_64               @@System
    Upgrade  docker-ce-cli-1:25.0.0-1.el8.x86_64           @plesk-ext-docker
    Upgraded docker-ce-cli-1:24.0.7-1.el8.x86_64           @@System
    Upgrade  docker-ce-rootless-extras-25.0.0-1.el8.x86_64 @plesk-ext-docker
    Upgraded docker-ce-rootless-extras-24.0.7-1.el8.x86_64 @@System
    Upgrade  docker-compose-plugin-2.24.1-1.el8.x86_64     @plesk-ext-docker
    Upgraded docker-compose-plugin-2.21.0-1.el8.x86_64     @@System

Code:
yum history undo 85

Accept changes ( by your risk )

Reboot server and docker start again. ( in my case )
 
@Ohya, Thanks for the quick response. This sounds like a good solution. In your case, the update was from the root user? Or from "plesk user"?
How can i view the updates from non-root users?
 

Attachments

  • user.png
    user.png
    42.7 KB · Views: 3
Here's another thread with a similar question regarding the storage driver. It may not be necessary to roll back the Docker installation.
 
But that happen one year a go

And documentation say problem starts with docker 23, this is new docker installed from 0 with plesk few months a go and installed in version 24.x

So plesk not care about this issue ?

Because its plesk standard install
 
In my case, v24 is alredy in overlay2

Code:
docker info |grep Storage
 Storage Driver: overlay2

And still fail when upgrade to 25

I not see storage errors in almalinux just some problems with nftables

So I think is diferent problem
 
Plesk does not develop Docker. It is a third-party application. The installation is done from the repository that your operating system provides.
 
Hi Peter, all problematic package comes from repo called plesk-ext-docker.repo, so, URLs are from docker.com but plesk add this repository we not decide use or not this repo, this comes with plesk extension :/
 
Hmm, that is strange. What's the content of the repository? Is it referring to a Plesk URL?
THis
Code:
[plesk-ext-docker]
name=docker extension repository
baseurl=https://download.docker.com/linux/centos/8/$basearch/stable
enabled=1
gpgcheck=1
gpgkey=https://download.docker.com/linux/centos/gpg
 
Back
Top