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
Currently we auto-pull images when needed, but we have no way of forcing another pull when an old container is there. This causes misc build issues when people forget to do it for a while when someone adds something new.
There should be a way to set lastImageDate or something in the manifest so that when people make breaking changes, it is there along with the repo it breaks. lal build could then do an image upgrade check.
The text was updated successfully, but these errors were encountered:
This could be solved by upstream docker, and we just depend on the behaviour. moby/moby#34394
I don't really see a good reason to not have this always enabled. If someone breaks a "latest" tag (and you hard depend on it), there's no way to unbreak yourself without proper change coordination anyway.
Currently we auto-pull images when needed, but we have no way of forcing another pull when an old container is there. This causes misc build issues when people forget to do it for a while when someone adds something new.
There should be a way to set lastImageDate or something in the manifest so that when people make breaking changes, it is there along with the repo it breaks. lal build could then do an image upgrade check.
The text was updated successfully, but these errors were encountered: