Bug fix Github actions out of disk error #575
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mwalker174
approved these changes
Jul 28, 2023
|
Thanks for the prompt review, @mwalker174.
There are larger runners under the paid plans; we can discuss how these can be useful moving forward as we currently have little headroom in disk size on current runners. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Github runners currently have ~15 GB disk space, and we run out of disk when building some of the base Docker images, as it will result in rebuilding many derived images. This PR adds the
--prune-after-each-imagetobuild_dockerinvocation to decrease disk usage. This flag was used in theTest Images Buildjob but missing from thePublishjob, which is a bug.The inconsequential change on the
samtools-cloud/Dockerfileis to trigger building and publishingsamtools-clouddocker image and all the derived images since thePublishjob had failed on #574, and the images were not published.