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
Tagging @bloomdt-uw who brought this to my attention
This is a meta-issue concerning cloudknot's use of Docker.
DockerImage.clobber(), and therefore Knot.clobber(clobber_image=True) seems to remove only the last layer of an image, not the entire thing.
Knot() instantiation with the same Docker image creates entire new images. The expected behavior is the create new tags of the same image.
Knot() instantiation is creating containers in addition to images. These containers are still running sometimes after clobber. There is no need to run containers locally so it is mysterious that they are there.
Tagging @bloomdt-uw who brought this to my attention
This is a meta-issue concerning cloudknot's use of Docker.
DockerImage.clobber(), and thereforeKnot.clobber(clobber_image=True)seems to remove only the last layer of an image, not the entire thing.Knot()instantiation with the same Docker image creates entire new images. The expected behavior is the create new tags of the same image.Knot()instantiation is creating containers in addition to images. These containers are still running sometimes after clobber. There is no need to run containers locally so it is mysterious that they are there.