Configurable Timeout for stack deployment

[yvernhurenat]

Besides some public containers we are also using some custom ones and in the end our stack has quiet some dependencies and health checks that are needed to bring it up.
Due to the startup time and health checks of some containers the total startup-time for the whole stack has increased to around 2-3 minutes. As the timeout in Portainer for a successful deployment can't be changed, I always get the "failed" message (although the stack continues to start successful at the end).
Would be nice, if we could set a maximum time to wait for Portainer until it displays this "failed" message.

[NV3S]

need it,especially several containers (in my environment is 4) in one yml/stack,and some performance issue on the host can couse some containers startup time increased,and portainer report unable to do something,then check the container list,they are created and some one is running

[Keiishu]

I have this all the time with huge stacks, even with the business edition. Would be really nice to have.

[OverDodo]

Same here, even for smaller stacks, like paperless-ngx with tika, the time to download all images etc. exceeds the timeout, so I get the error.

[Gecko-with-a-hat]

The same over here. Startup time for my "metrics" stack (loki, promtail, grafana, graylog, elasticsearch, etc.) takes a few minutes to start/update. For over a year I thought there was an issue with deployment. Only today I found out it's simply Portainer timing out. If configurable timeout time is a big hastle, it would be awesome to just say something like this in the error: "unable to create stack: Portainer deploy timeout reached".

[Nick-Portainer]

Hey, thanks for raising this. I will raise this with our product team for discussion.

[Nick-Portainer]

internal: PCT-354

[neilenns]

Just adding my "yes please" to the request. My stack isn't too big but it's not running on the beefiest of machines and I frequently get the failure message even though things are starting up just fine.

[deviantony]

Are you guys deploying on local environments by any chance? Or on remote agent environments?

[OverDodo]

For me, just local.

[neilenns]

Same, just local.

[Gecko-with-a-hat]

Local and remote, but the issue has only arisen on local environment. The stacks on remote environments are small and the containers quite lightweight.

[EHRETic]

Hi there,

Would love such feature too, I've often problem with Netbox stack that takes some time tostart/update to newer version.
Problems comes the same on local & remote agent.