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

ARM docker Image #357

Open
vncloudsco opened this issue Jun 2, 2022 · 7 comments
Open

ARM docker Image #357

vncloudsco opened this issue Jun 2, 2022 · 7 comments

Comments

@vncloudsco
Copy link

Dear: all contributors

we know that your software already support ARM however i see its docker image is not updated. is there any guide to help me do it or can you update the docker hub image?

Ref: https://blog.zulip.com/2022/03/29/zulip-5-0-released/

@maltegrosse
Copy link

multi arch images would be great! its possible to setup easily with github actions

klardotsh added a commit to klardotsh/docker-zulip that referenced this issue Feb 23, 2023
Allow building amd64+arm64 multiarch images locally for those brave
enough to experiment with them.

Refs zulip#357.
klardotsh added a commit to klardotsh/docker-zulip that referenced this issue Feb 23, 2023
Allow building amd64+arm64 multiarch images locally for those brave
enough to experiment with them.

Refs zulip#357.
klardotsh added a commit to klardotsh/docker-zulip that referenced this issue Mar 24, 2023
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 zulip#357.
klardotsh added a commit to klardotsh/docker-zulip that referenced this issue Mar 24, 2023
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 zulip#357.
klardotsh added a commit to klardotsh/docker-zulip that referenced this issue Mar 24, 2023
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 zulip#357.
klardotsh added a commit to klardotsh/docker-zulip that referenced this issue Mar 24, 2023
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 zulip#357.
klardotsh added a commit that referenced this issue Mar 24, 2023
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.
klardotsh added a commit to klardotsh/docker-zulip that referenced this issue Mar 24, 2023
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 zulip#357.
klardotsh added a commit to klardotsh/docker-zulip that referenced this issue Mar 24, 2023
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 zulip#357.
klardotsh added a commit that referenced this issue Mar 28, 2023
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.
@leadvic
Copy link

leadvic commented Sep 19, 2023

it's been more than a year since this, just to know are there any update or hope for those with ARM?

Thank you before hand!

@klardotsh
Copy link
Member

klardotsh commented Sep 19, 2023

You'll want to ping the team about #397, the re-opened flavor of the PR linked to this issue above. I no longer work for Zulip and highly doubt I'll have the appropriate time to do much with that PR as an external contributor any time soon, but it appears there's not a whole lot of feedback on it to address before it'll be in a merge-ready state (to my eye, and with the understanding that my knowledge of the Zulip codebase context ends at the end of March when I changed dayjobs).

@dretsa
Copy link

dretsa commented Jun 22, 2024

Are there any updates on this? Would be great to be able to run on t4g instances on AWS!

@cb0s
Copy link

cb0s commented Oct 9, 2024

Any updates? :) Would be great to get this installed on an ARM VPS! 😄

@cb0s
Copy link

cb0s commented Oct 9, 2024

For anyone who cannot wait (like me), simply build the image yourself on the target machine. For this, navigate to the folder to which you cloned docker-zulip:

$ pwd
/home/dummy-user/docker-zulip
$ # this can take several minutes - in my case it was ~50 min on a relatively new server
$ # you can choose (almost) any tag you like after -t
$ docker buildx build -t zulip-arm:latest .

Now edit the docker-compose.yml with your favourite editor or vim:

$ vim docker-compose.yml

Change the image of zulip from zulip/docker-zulip:<version> to the tag you chose earlier (zulip-arm:latest in this case).

You can probably also do this in one step changing image to build in the docker compose file. You will find more information about this in the official docker documentation.

@klardotsh
Copy link
Member

You can also cross-build from either architecture to the other. This is what the build_and_push_image.sh from #397 does: builds ARM64 images from AMD64 hosts. That script was designed to be able to push to ~any registry for ~any architectures or tags by changing environment variables.

The branch is a year and a half old and at this point I don't know what kind of rebase pain someone would be in for to stack it onto current trunk, but I suspect at least that script could be cherry-picked and used by anyone interested, still.

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

No branches or pull requests

6 participants