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 molecule does not tag builded images which makes impossible to identify which contrainers or images from a docker host were created by it.
Same issue applies to other providers and we need to assure that we add at least one tag that would allow us to identify molecule managed resources.
Once we do start tagging resources it will be possible to implement a molecule reset feature that would cleanup lefovers, from current runs or any other molecule runs.
While implementing this we can safely assume that we cannot rely on any local data persistency, all the information should be contained in each used provider.
This discussion was converted from issue #2142 on June 05, 2021 09:35.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
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
-
Currently molecule does not tag builded images which makes impossible to identify which contrainers or images from a docker host were created by it.
Same issue applies to other providers and we need to assure that we add at least one tag that would allow us to identify molecule managed resources.
Once we do start tagging resources it will be possible to implement a
molecule reset
feature that would cleanup lefovers, from current runs or any other molecule runs.While implementing this we can safely assume that we cannot rely on any local data persistency, all the information should be contained in each used provider.
Beta Was this translation helpful? Give feedback.
All reactions