Make it possible to run builder using podman.#186
Open
Andykl wants to merge 18 commits into
Open
Conversation
Ubuntu latest git does not support that, and those repos are not big anyway.
This prevent spawning unbound amount of threads and periodically return execution to main thread so docker does not hang.
Andykl
force-pushed
the
wrap-in-podman
branch
from
91c4ec3 to
ab9309f
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
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.
This PR is made on top of #181 and #183.
This PR allow to build Ren'Py on Windows machine using Podman. The build process after podman is installed and configured looks like that:
podman build -f Dockerfile.base -t renpy-build-base:latest .podman compose buildpodman compose run renpy-build --platforms windowsFirst build takes about 40 min on my machine. When build artefacts are present in tmp rebuild takes about 2 minutes.
This PR uses 2 layers, where first layer is the system with all the system level packages installed. Its size is about 3GB and should not change often. Second layer copies build files and binds to cache volumes. It could change more freely, but copy is needed so there is no Windows-Linux IO.
The system uses 3 volumes to cache in VM build artefacts, venv and ccache output, and is needed for fast incremental builds. Those could be combined in one volume tho.