-
Notifications
You must be signed in to change notification settings - Fork 56
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
Publish docker images via GHA #1134
Publish docker images via GHA #1134
Conversation
> The workflow is not valid. .github/workflows/docker.yml: Anchors are not currently supported. Remove the anchor 'buildx
already exists at the org level in the primary sytest repo
interesting to know it's possible, but I don't understand what it's doing and it hasn't saved any time. One for a rainy day.
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.
This looks sensible to me (don't forget to remove dmr/publish-docker-images
from the branch list before you merge ;p), but a couple of questions which probably want feedback from someone more opinionated.
strategy: | ||
matrix: | ||
include: | ||
- base_image: ubuntu:bionic |
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.
I don't know if this PR is the time for this or not, but @richvdh told me not to use bionic
when I was asking about which image to use — because it's old.
Should we be bumping this to something like focal
(20.04 LTS) (or hirsute
[21.04] though probably not this one because non-LTS releases run out of life fairly quickly)?
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.
I generally prefer debian to ubuntu for this sort of thing - it has a longer support lifetime than the non-LTS ubuntus, and is bettter maintained than the LTS ones
suggest debian:bullseye-slim
.
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.
Can do. (I was just trying to replicate the existing behaviour as faithfully as I could.)
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.
On second thoughts, I'll make that a second PR.
LGTM otherwise |
Co-authored-by: reivilibre <38398653+reivilibre@users.noreply.github.com>
I tested this by running on my repo with an access token for my dockerhub account.
This run shows what a successful workflow should look like.
To publish these images to
matrixdotorg
we'll need an access token secret in this repository. I've requsted that in vector-im/sre-internal#162.