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
When I'm doing local testing of Linux builds, each invocation of .circleci/run_docker_build.sh leaves behind a dead Docker container when the build finishes (successfully or not). These are a bit tedious to clean up. I have also not found that it is that important to preserve the containers, since all of the useful state is in the build_artifacts directory that has its own life outside of the container. So, should we add a --rm flag to the docker run command to cause it to automatically remove the containers when they're done running?
If what I wrote above is all correct, I really don't think there's any downside, but perhaps I'm missing something.
The text was updated successfully, but these errors were encountered:
When I'm doing local testing of Linux builds, each invocation of
.circleci/run_docker_build.sh
leaves behind a dead Docker container when the build finishes (successfully or not). These are a bit tedious to clean up. I have also not found that it is that important to preserve the containers, since all of the useful state is in thebuild_artifacts
directory that has its own life outside of the container. So, should we add a--rm
flag to thedocker run
command to cause it to automatically remove the containers when they're done running?If what I wrote above is all correct, I really don't think there's any downside, but perhaps I'm missing something.
The text was updated successfully, but these errors were encountered: