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
Hello , im just curious if this is on purpose or found something here..
The use case is the following:
i have a running container with image name test_image.
While have that running ,i m building a new version of the image with updates.
dockerode reports that image in running container as
Image: 'sha256:12497d04d69de618dfc800.....' ( before new build was test_image )
while docker inspect
reports it as test_image .
I understand the when we are creating a new version of an image docker tags the new one with the name , but i think we are loosing some info there.
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
-
Hello , im just curious if this is on purpose or found something here..
The use case is the following:
i have a running container with image name test_image.
While have that running ,i m building a new version of the image with updates.
dockerode reports that image in running container as
Image: 'sha256:12497d04d69de618dfc800.....' ( before new build was test_image )
while docker inspect
reports it as test_image .
I understand the when we are creating a new version of an image docker tags the new one with the name , but i think we are loosing some info there.
Is that the desired behavior on this scenario ?
Beta Was this translation helpful? Give feedback.
All reactions