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
The Container.image property is a string representing the image ID, rather than an Image instance. This is consistent with all fields of inspect output, which is simply parsed via pydantic, however in the case of the field being a simple ID we could use this to construct a python-on-whales object for the user's convenience.
Doing a docker.image.inspect() has a runtime cost. If we do it, we'll need to use the lazy loading features of python-on-whales.
I'll need to think about it, there are qui a few area that this can affect, because we could argue that the same could be done for volumes, networks, etc
The
Container.image
property is a string representing the image ID, rather than anImage
instance. This is consistent with all fields of inspect output, which is simply parsed via pydantic, however in the case of the field being a simple ID we could use this to construct a python-on-whales object for the user's convenience.The problem is backwards compatibility... Perhaps something for v1.0?
The same consideration exists for the new
Container.pod
andPod.containers
properties, see LewisGaul@6ffcf45.The text was updated successfully, but these errors were encountered: