You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
When creating a stack via the API using compose content in the request payload,
Portainer does not appear to re-pull images if the image tags already exist
locally. The update stack endpoint supports a pullImage / force pull option,
but the create stack endpoint does not seem to expose an equivalent parameter.
Describe the solution you'd like
The create stack API should optionally support the same image-pull behavior as
the update/redeploy API, for example pullImage=true.
Describe alternatives you've considered
Add new stack via API and immediately update the stack via the update endpoint.
Additional context
Use case:
Automation that creates a stack if missing, otherwise updates it. The update
path can force-pull images, but the create path cannot, so first-time deployment
may use stale local images for mutable tags such as latest.
But: updating the stack via webUI does the re-pull.
I discovered btw. that the image's created date is 1970-01-01 01:00:00... Maybe this is related to this behavior?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe
When creating a stack via the API using compose content in the request payload,
Portainer does not appear to re-pull images if the image tags already exist
locally. The update stack endpoint supports a pullImage / force pull option,
but the create stack endpoint does not seem to expose an equivalent parameter.
Describe the solution you'd like
The create stack API should optionally support the same image-pull behavior as
the update/redeploy API, for example pullImage=true.
Describe alternatives you've considered
Add new stack via API and immediately update the stack via the update endpoint.
Additional context
Use case:
Automation that creates a stack if missing, otherwise updates it. The update
path can force-pull images, but the create path cannot, so first-time deployment
may use stale local images for mutable tags such as latest.
But: updating the stack via webUI does the re-pull.
I discovered btw. that the image's created date is 1970-01-01 01:00:00... Maybe this is related to this behavior?
Beta Was this translation helpful? Give feedback.
All reactions