• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Issue Change default networks for docker extension

martin.g

New Pleskian
Server operating system version
Almalinux 9.5
Plesk version and microupdate number
18.0.68#2
Hi,

I recently installed docker on plesk by installing the docker extension.
By default it adds two networks:
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
172.18.0.0/16 dev br-aafb58fc62b3 proto kernel scope link src 172.18.0.1 linkdown
They are conflicting with some of my regular subnets. What is best practice to change those two networks on plesk appliance? I did not find a possibility within GUI, but I don´t want that updates etc reset to default networks.

Could someone assists please?

Regards
Martin
 
Back
Top