• 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!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

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