• 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.

Forwarded to devs Docker Input Field Disallows "=" Signs to Apply Config Variables

J.Wick

Regular Pleskian
TITLE:
Docker Input Field Disallows "=" Signs to Apply Config Variables​
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
Plesk Onyx Version 17.8.11 Update #60, CentOS Linux 7.6.1810 (Core)​
PROBLEM DESCRIPTION:
When trying to apply setting options for a container, the "=" is disallowed preventing proper setup and launching of Docker containers producing the error...

The value of an environment variable cannot contain the '=' (equal) sign.​
STEPS TO REPRODUCE:
  1. Open Docker Container Settings (million12/varnish)
  2. Enter "-p default_ttl=120" into the VARNISHD_PARAMS variable
  3. Hit OK
  4. Error Message is produced.
ACTUAL RESULT:
Error.

The value of an environment variable cannot contain the '=' (equal) sign.​
EXPECTED RESULT:
We should be able to place as many options as needed and have them saved successfully when clicking OK. Stop form validating the field.​
ANY ADDITIONAL INFORMATION:
Using the command line, I can set all these variables...but what the point of using Plesk then?​
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug​
 

Attachments

  • bug.png
    bug.png
    85.5 KB · Views: 4
Thank you!
The bug was confirmed and submitted as EXTDOCKER-84
 
Fixed!

1.4.3 (1 November 2019)
[...]
[-] Entering the equals sign (=) as a part of an environment variable in the Docker extension no longer results in an error. (EXTDOCKER-84)
 
Back
Top