-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: use standard Docker build Actions, enable builds for ARM architecture #985
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this nice PR.
First I had a deja vu feeling, but that was #882 (comment)
I will just pull as is, and see if the docker is still working on my machine (i.e. amd64).
.github/workflows/docker-release.yml
Outdated
uses: docker/build-push-action@v3 | ||
with: | ||
context: . | ||
push: ${{ github.event_name != 'pull_request' }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
push: ${{ github.event_name != 'pull_request' }} | |
push: true |
Because the whole workflow is not triggered on pull requests.
.github/workflows/docker-release.yml
Outdated
id: meta | ||
uses: docker/metadata-action@v4 | ||
with: | ||
github-token: ${{ secrets.GITHUB_TOKEN }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
github-token: ${{ secrets.GITHUB_TOKEN }} |
I think this is not needed.
[why] Credentials not needed (I guess). Workflow is never run on pull-requests, so no check needed. Signed-off-by: Fini Jastrow <[email protected]>
Hey sorry just saw this it's midnight here but I'll fork the repo, create a docker hub account and test it out using my own token. Feel free to temporarily revert if it's causing any issues! |
Ah, I managed to create the arm thing 🎉 via commit But maybe you can try to patch a font with that. And report which |
ooohhhh I didn't release it needed the platform there as well! Good spotting and thanks! I'll be testing it out shortly. |
Seems to work fine, only error is about iconv encoding - but that won't be ARM build related. I've run the patched fonts through font book and they validated without issue.
|
Ah, we base the docker on Alpine iirc, and they use musl's The relevant code is here: https://github.com/fontforge/fontforge/blob/-/fontforge/encoding.c#L196 |
CI: Use standard Docker build Actions, enable builds for ARM architecture
Description
Refactor docker-release (aka build and push) workflow to use the standard Docker Github Actions.
Requirements / Checklist
What does this Pull Request (PR) do?
This adds the following features:
How should this be manually tested?
Any background context you can provide?
I went to run the nerd-fonts patcher and found the provided container image was only built for AMD64, many modern computers are ARM64 hence this PR.
https://github.com/marketplace/actions/build-and-push-docker-images
What are the relevant tickets (if any)?
Screenshots (if appropriate or helpful)