8000 Pre-built ARM64 images of CockroachDB -> christoofar/cockroachdb-arm64 · Issue #62903 · cockroachdb/cockroach · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Pre-built ARM64 images of CockroachDB -> christoofar/cockroachdb-arm64 #62903

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.

Sign up for GitHub

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

Jump to bottom
Closed
christoofar opened this issue Mar 31, 2021 · 8 comments
Closed

Pre-built ARM64 images of CockroachDB -> christoofar/cockroachdb-arm64 #62903

christoofar opened this issue Mar 31, 2021 · 8 comments
Labels
B-unsupported-arch Non-x86_64 architectures: PPC, MIPS, etc C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) O-community Originated from the community X-blathers-untriaged blathers was unable to find an owner

Comments

@christoofar
Copy link
christoofar commented Mar 31, 2021 •
edited by cockroach-jira-scripts
Loading

Hi there

I realize this isn't a priority for the crdb team, but I've made a simplified and much easier to build version of crdb on arm64 available -> https://hub.docker.com/repository/docker/christoofar/cockroachdb-arm64

I try to update this myself, it's compiled on a Raspberry PI 400. But you can also grab the GitHub repo and make your own image if you wish. I run this build against a 40GB database I maintain and it behaves just like the x86 build.

Jira issue: CRDB-6203
@christoofar christoofar added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label Mar 31, 2021
@blathers-crl
Copy link
blathers-crl bot commented Mar 31, 2021

Hello, I am Blathers. I am here to help you get the issue triaged.

It looks like you have not filled out the issue in the format of any of our templates. To best assist you, we advise you to use one of these templates.

I was unable to automatically find someone to ping.

If we have not gotten back to your issue within a few business days, you can try the following:

  • Join our community slack channel and ask on #cockroachdb.
  • Try find someone from here if you know they worked closely on the area and CC them.

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan.

@blathers-crl blathers-crl bot added O-community Originated from the community X-blathers-untriaged blathers was unable to find an owner labels Mar 31, 2021
@knz knz added the B-unsupported-arch Non-x86_64 architectures: PPC, MIPS, etc label Apr 13, 2021
@knz
Copy link
Contributor
knz commented Apr 13, 2021

Link to the repo: https://github.com/christoofar/cockroachdb-arm64

@knz
Copy link
Contributor
knz commented Apr 13, 2021

@christoofar looking at your Dockerfile, it looks like you were able to build from sources "out of the box", without any patches. Is this correct?

@FireMasterK
Copy link

According to #20433 (comment), building arm64 images are possible, so why not have officially built images?

@knz
Copy link
Contributor
knz commented Jun 21, 2021

because we're not building images unless they get the same amount of testing and QA, and organizing testing and QA for a new platform costs $$ and that hasn't been a priority so far.

@christoofar
Copy link
Author
christoofar commented Jun 27, 2021 •
edited
Loading

@christoofar looking at your Dockerfile, it looks like you were able to build from sources "out of the box", without any patches. Is this correct?

Yes. I pull the .ZIP of the source code and then just make a build from there.

I have recently modified the Dockerfile to use a golang docker image (with a newer compiler) to do the build.

My crdb test databases at home are all running on ARM64.

@christoofar
Copy link
Author

because we're not building images unless they get the same amount of testing and QA, and organizing testing and QA for a new platform costs $$ and that hasn't been a priority so far.

Understandable. Luckily ARM64 with the current code base (as of this writing) works OK, anyone who would be using it would need to understand that platform (and whatever issues that are not reproducible on x64) shouldn't expect to get any mainline support.

@kenliu-crl
Copy link
Contributor

Hi. We are posting updates on ARM64 support to these other active issues.

This is the latest update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
B-unsupported-arch Non-x86_64 architectures: PPC, MIPS, etc C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) O-community Originated from the community X-blathers-untriaged blathers was unable to find an owner
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@knz @christoofar @FireMasterK @kenliu-crl
0