Open
Conversation
f311713 to
f3767c5
Compare
Author
|
I've forked the docker image that I initially used and updated its base to ubuntu 22.04. I am now able to reproduce the failing build that I saw in #17 so I think it would be good to use my fork instead. This allows us to get the same results locally as we get in workflows. |
f3767c5 to
1155a3c
Compare
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
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.
I'm working from different machines across Linux, Windows and macOS. For me it's quite convenient to have the build dependencies in a Dockerfile so that I don't have to deal with platform specific quirks during dependency setup on every individual system.
If you think this might be useful to others, please let me know whether you'd like any changes to be incorporated (file naming for example).