-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Docker images #25
base: main
Are you sure you want to change the base?
Docker images #25
Conversation
* Change base image architecture and version * Remove version from certbot-dns-desec
* Based on Certbot 2.2.0 now * Builds certbot-dns-desec Docker from local sources
* Bump to certbot 2.2.0 * Link images together under "latest" tag
@Cub0n is there a way to test your Github action without releasing a package? I'd like to get a feeling of this works before we publish. @peterthomassen I had to create a new PR with (mostly) @Cub0n's code, but now that requires your review as per our repo rules. Can you take a look, please? :) |
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.
In addition to the inline comments:
Building the Python package from scratch may not be reproducible due to package dependencies. We could consider always pulling the package of the same version from PyPi, but I'm not sure how that could be done.
Also, suggesting to squash before merging.
run: | | ||
docker buildx build . -f Dockerfile --platform ${{ matrix.cmd.platforms }} --push \ | ||
-t ${{ env.REGISTRY }}/${{ env.IMAGE_REPO }}:${{ matrix.cmd.arch }}-${{ env.IMAGE_TAG }} \ | ||
-t ${{ env.REGISTRY }}/${{ env.IMAGE_REPO }}:${{ matrix.cmd.arch }}-latest \ |
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.
Are we assuming that v*
tags are added in strongly increasing order? If not, -latest
should only be pushed on main
branch.
docker manifest create ${{ env.REGISTRY }}/${{ env.IMAGE_REPO }}:latest \ | ||
--amend ${{ env.REGISTRY }}/${{ env.IMAGE_REPO }}:amd64-latest \ | ||
--amend ${{ env.REGISTRY }}/${{ env.IMAGE_REPO }}:arm32v6-latest \ | ||
--amend ${{ env.REGISTRY }}/${{ env.IMAGE_REPO }}:arm64v8-latest | ||
docker manifest push ${{ env.REGISTRY }}/${{ env.IMAGE_REPO }}:latest |
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.
Are we assuming that v*
tags are added in strongly increasing order? If not, -latest
should only be pushed on main
branch.
Hello @nils-wisiol,
no, unfortunately I was not able to test it without producing packages. Therefore I had/have a lot of during testing. |
No description provided.