Nick Wilkinson

icon company Portainer icon location New Zealand icon location Customer Support Team Lead @ Portainer

Results 225 comments of Nick Wilkinson

[Reopen][7676] Allow starting of stack on portainer startup

@leleobhz, can you please help me understand what the actual issue is here? How Podman handles restarts is not controlled by Portainer. I am just wanting to understand your expectations

Portainer does not substitute values inside compose file with environment variables from an dotenv file

Hi @papaj-na-wrotkach, There are two different things to clarify here. When it comes to setting environment variables the way you’re doing it, this is called variable substitution—where you’re setting Docker...

Unable to browse volumes with Portainer 2.22.0

Hey @pnbecker Can you please confirm the agent version of the environment having the issue? Bug confirmed ```internal: BE-11216```

Unable to browse volumes with Portainer 2.22.0

@mmjc23 and @glenndehaan Are you running Swarm as well or Standalone? We have an active bug ticket open for this and is being worked on

Confusing typeable fields when exposing secrets via Add with Form in Kubernetes

Thanks @hookenz, I have raised this internally ```internal: FR-561```

[BUG] Attaching a console always sends 'export LANG=C.UTF-8' even when target console is not sh

Hi @jogerj Thank you for reporting this, I confirmed this with the compose you provided. I am raising this internally `internal: EE-7293`

pulling from custom registry credentials are ignored

Hi @felixlabrot Do you have multiple custom registries added?

pulling from custom registry credentials are ignored

@felixlabrot Can you please give steps to reproduce this as close as possible. What registry are you using etc so I can try replicate this.

pulling from custom registry credentials are ignored

Thanks all. I have raised this internally for investigation. ```internal: BE-11674```

pulling from custom registry credentials are ignored

@rafaelreis-r Thanks for the bump. I have been keeping an eye on this and yes we are planning a fix for this in a future release. I can not provide...