Add GitHub Actions workflow to build Docker build env#446
Merged
Conversation
It's much faster to build and upload an image from a GitHub Actions runner than to build locally and then upload from a remote connection.
This was referenced May 17, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
It's much faster to build and upload an image from a GitHub Actions runner than to build locally and then upload from a remote connection.
To keep this simple, this workflow will only run on demand. It will need to be part of the default branch (
main) before it can be run on demand.The typically workflow might be to update the
Dockerfileand the tag in thebuildDockerBuildEnvworkflow, and then run it, from the branch, to build the new image. Update the image tag used by the runners in a followup commit, and then open a PR.Related: