The current implementation assumes that the Docker images for a build are unique to that build and will try to remove the images when the build is destroyed. Although the error it returns is printed but otherwise ignored, this is an invalid assumption particularly in more complicated deployment environments where seed reuse may be significant.
The current implementation assumes that the Docker images for a build are unique to that build and will try to remove the images when the build is destroyed. Although the error it returns is printed but otherwise ignored, this is an invalid assumption particularly in more complicated deployment environments where seed reuse may be significant.