Add github action to build and release containers#3841
Open
ilkka-ollakka wants to merge 1 commit intobookwyrm-social:mainfrom
Open
Add github action to build and release containers#3841ilkka-ollakka wants to merge 1 commit intobookwyrm-social:mainfrom
ilkka-ollakka wants to merge 1 commit intobookwyrm-social:mainfrom
Conversation
hughrun
added
deployment
development
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
3 participants
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.
Description
Split from #3636
This PR will enable building of bookwyrm container on main branch and tags. Tag-builds also get latest-tag.
So following container tags are present:
Containers are stored in repository container registry but not used yet in docker-compose.yml. I'll open separate PR to take the containers into use, so this flow can be tested/tuned if needed before it is widely in use.
It also has manual dispatch, so you can start manually build for specific tag if needed.
Currently amd64 and arm64 containers are build, so for example 32bit raspberry pi can't use those.
Containers are also build from PR phase, but not published.
This doesn't yet change how containers are used, so the release flow is still that repo is checked out and containers are build locally by default.
What type of Pull Request is this?
Does this PR change settings or dependencies, or break something?
Details of breaking or configuration changes (if any of above checked)
Documentation
Tests