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
If a stack contains both containers with images from e.g. dockerhub and local images, the reload and pull new version fail, because it cannot pull a local image.
Either
Ignore failure of non-pullabiliy for local images
OR
As portainer can determine if an image is a local or a remote in order to check if it is the newest version, then use the same logic to determine which images should be renewed.
The text was updated successfully, but these errors were encountered:
Thank you for the information. Upon review with Product, this is a known issue and has been logged internally for resolution. I do not yet have a release or timeframe.
This issue has been marked as stale as it has not had recent activity, it will be closed if no further activity occurs in the next 7 days. If you believe that it has been incorrectly labelled as stale, leave a comment and the label will be removed.
:
This issue has been marked as stale as it has not had recent activity, it
will be closed if no further activity occurs in the next 7 days. If you
believe that it has been incorrectly labelled as stale, leave a comment and
the label will be removed.
—
Reply to this email directly, view it on GitHub
<#8038 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACK5JF2EBKT2ZKQKCJDKBV3XUN35PANCNFSM6AAAAAAR5ZHC4U>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
If a stack contains both containers with images from e.g. dockerhub and local images, the reload and pull new version fail, because it cannot pull a local image.
Either
Ignore failure of non-pullabiliy for local images
OR
As portainer can determine if an image is a local or a remote in order to check if it is the newest version, then use the same logic to determine which images should be renewed.
The text was updated successfully, but these errors were encountered: