Create Stack - ENV params parsing error

[zafrirron]

Bug description
Fail to deploy a stack - environemnt variable parsing error

Expected behavior
simple key value parser for the following variable (replace USER/PASS/DB with yours):
MONGO_URI='mongodb+srv://USER:PASS@cluster0.1x6jg.mongodb.net/DB?retryWrites=true&w=majority'

Portainer Logs
Provide the logs of your Portainer container or Service.
You can see how here
No need a parser werror on web interface

Steps to reproduce the issue:

1. Go to: create stack
2. Click on: advacnced mode; paste your variables (including the MONGO_URI var from above)
3. Scroll down to: change back to simple mode
4. See error: variable key/value fails

Technical details:

• Portainer version: 2.6.3
• Docker version (managed by Portainer): v20.10.8
• Kubernetes version (managed by Portainer): N/A
• Platform (windows/linux): windows
• Command used to start Portainer (docker run -p 9443:9443 portainer/portainer):
• Browser: chrome
• Use Case (delete as appropriate): Using Portainer at Home
• Have you reviewed our technical documentation and knowledge base? Yes

Additional context
using the same compose file from linux command prompt - work like a charm...

[Rockz1152]

I've noticed this too, if an environment variable line contains more than one "=" signs, Portainer seems to parse the value from the last "=" sign instead of the first. Compared to docker-compose which seems to parse the value after the first "=" sign.

[zafrirron]

I've noticed this too, if an environment variable line contains more than one "=" signs, Portainer seems to parse the value from the last "=" sign instead of the first. Compared to docker-compose which seems to parse the value after the first "=" sign.

Correct, try a='b=c=d=e'

[Rockz1152]

Quotation marks didn't work for me. I believe that is per the syntax rules for env files. https://docs.docker.com/compose/env-file/

There is no special handling of quotation marks. This means that they are part of the VAL.

[huib-portainer]

if an environment variable line contains more than one "=" signs, Portainer seems to parse the value from the last "=" sign instead of the first

That UI issue has been solved by #5395

You can give it a try by using the image portainerci/portainer:develop.
Please let us know how that's working for you.
Note that this is a development build and should not be used in a production environment.

As for the original report, try it without quotes.

e.g. this test stack:

version: '3'
services:
  nginx-env-service:
    image: nginx:alpine
    environment:
      MONGO_URI: "${MONGO_URI}"

With the env var:

Results in

[Rockz1152]

Just tested with portainerci/portainer:develop and everything is working great for me.

[zafrirron]

Checked the portainerci/portainer:develop image, looks like the bug was fixed....thx