Skip to content
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

Automate publishing multiarch images to GHCR (migrate away from Docker Hub) #397

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

klardotsh
Copy link
Member

@klardotsh klardotsh commented Mar 28, 2023

This reopens #395 in-house again, similar to #396, which now can't be reopened due to a force-push. The 403s found in this CI run are a forked-repo permissions problem; this PR suffers no such issues and can publish to GHCR successfully.

Supercedes #390 by building multiarch images in GHCR rather than depending on local workstation builds.

Blockers: https://github.com/orgs/zulip/packages/container/package/zulip needs to be made public, and I need to verify that this repo actually has permissions to push to that registry (while I'm an admin of the registry, I'm not an admin of this repo, so can't double-check the secrets plumbing behind the scenes that I vaguely recall being a thing to do here).

@klardotsh klardotsh changed the title (Testing for now) Automate publishing multiarch images to GHCR (migrate away from Docker Hub) Automate publishing multiarch images to GHCR (migrate away from Docker Hub) Mar 28, 2023
@klardotsh
Copy link
Member Author

Before I go making the changes to run this workflow using tags instead of the version file, saving this link to a successful CI run which generated this GHCR manifest

In light of recent changes to Docker Hub, move our Docker images into
GHCR which integrates more tightly with GitHub flows we already use
throughout the Zulip org. Since it's near-trivial to do so at the same
time, add officiallly-supported ARM64 builds.

Resolves #357.
# -- Pull policy for Zulip docker image.
# Ref: https://kubernetes.io/docs/user-guide/images/#pre-pulling-images
pullPolicy: IfNotPresent
# -- Zulip image tag (immutable tags are recommended)
tag: "6.1-0"
tag: "6.1-1"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We now can't do this version bump without a tag, so it needs to come after the PR merges. The commit message needs top be massaged accordingly, I think.

@@ -86,7 +86,7 @@ spec:
- name: postgresql-persistent-storage
mountPath: /var/lib/postgresql
- name: zulip
image: zulip/docker-zulip:6.1-0
image: ghcr.io/zulip/zulip:6.1-1
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ditto above.

Comment on lines +14 to +18
docker pull ghcr.io/zulip/zulip:6.1-1
```

- Current Zulip Server version: `6.1`
- Current Docker image version: `6.1-1`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's leave these as 6.1-0 for now, and do a version bump tag separately.

@klardotsh klardotsh mentioned this pull request Sep 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants