Portainer.io
Configurable Timeout for stack deployment #9798
Replies: 10 comments 5 replies
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
I have this all the time with huge stacks, even with the business edition. Would be really nice to have. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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". |
Beta Was this translation helpful? Give feedback.
-
|
Hey, thanks for raising this. I will raise this with our product team for discussion. |
Beta Was this translation helpful? Give feedback.
-
|
internal: PCT-354 |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Are you guys deploying on local environments by any chance? Or on remote agent environments? |
Beta Was this translation helpful? Give feedback.
-
|
For me, just local. |
Beta Was this translation helpful? Give feedback.
-
|
Same, just local. |
Beta Was this translation helpful? Give feedback.
-
|
Local and remote, but the issue has only arisen on local environment. The stacks on remote environments are small and the containers quite lightweight. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, Would love such feature too, I've often problem with Netbox stack that takes some time tostart/update to newer version. |
Beta Was this translation helpful? Give feedback.
-
|
Would love this issue as my internet is so slow that it times out due to how long it takes to download containers. |
Beta Was this translation helpful? Give feedback.
-
|
Just a note, the timeout error does not actually mean the deployment really failed – at least in my case. It continues in the background, and at some point it will be successful. |
Beta Was this translation helpful? Give feedback.
-
|
Me too
-------- Original Message --------On 11/25/24 23:57, Qhilm wrote:
Just a note, the timeout error does not actually mean the deployment really failed – at least in my case. It continues in the background, and at some point it will be successful.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
[
{
***@***.***": "http://schema.org",
***@***.***": "EmailMessage",
"potentialAction": {
***@***.***": "ViewAction",
"target": "#9798 (reply in thread)",
"url": "#9798 (reply in thread)",
"name": "View Discussion"
},
"description": "View this Discussion on GitHub",
"publisher": {
***@***.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
|
Beta Was this translation helpful? Give feedback.
-
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.
Beta Was this translation helpful? Give feedback.
All reactions