portainer: [BUG] UI - Unable to edit Env Vars on docker-standalone

Bug description when changing env vars in stacks, save button stays greyed out.

Expected behavior When changing env var, save settings button should activate

Portainer Logs nothing of significance

Steps to reproduce the issue:

Have stack working and deployed
Edit stack
Change env var
“Save Settings” button remains greyed out.

Technical details:

Portainer version: 2.16.1
Docker version (managed by Portainer): 20.10.21
Platform (windows/linux): linux x86_64 CentOS Linux 7 (Core)
Browser: Chrome Version 107.0.5304.110 (Official Build) (64-bit)
Use Case: Using Portainer in a Commercial setup.
Have you reviewed our technical documentation and knowledge base? Yes

Additional context hacking the button in the UI by using the Inspector and removing disabled=disabled allows it to be clicked and then saving works.

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 15

Most upvoted comments

@rijnhard

I wanted to follow up on this request. @cf-sewe provided additional details regarding the issue. I am now able to reproduce.

[1] Create Stack via GitRepo in 2.14.2 [2] Upgrade to 2.15.1 >> You can edit the Environment Variables [3] Upgrade to 2.16.2 >> You can not edit the Environment Variables.

The git credentials appear to not be migrated in 2.16.xx series. I am logging an internal issue to resolve. I do not yet have a timeline or release.

Workaround: [1] Advanced Configuration >> Re-enter git token/password [2] You can now edit the Environment Variables

tamarahenson on Nov 29, 2022

@Magnacoder thats usually dependant on the actual container in question, with some containers (especially database containers) it only reads the env vars on the initial DB creation and then they are pointless.

Some containers like pgadmin only read SOME variables at creation (like admin user & pass) and won’t read those values thereafter.

rijnhard on Apr 2, 2023

So I can confirm the workaround did the trick.

Just as a backlog of the events (if I remember them correctly):

on 2.16.0 I created the stack that was linked to a private repo (with git credentials working).
upgraded to 2.16.1, git credentials still working.
upgraded to 2.16.2, switched to BE to have OAuths and disable local logins.
Wasn’t able to change the deployed stack (same on 2.17.0).

I’m not 100% sure what could have been the problem on point 3, but most likely the upgrade one. (git credentials were saved under the stack and not the user).

Sandros94 on Feb 9, 2023