-
-
Notifications
You must be signed in to change notification settings - Fork 226
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 containers for more platforms #1084
Comments
Since there are no existing kroki images for arm64, should I be building my own ARM image locally? Is it simple to do? |
The "gateway container" In your logs, you can see that the application ("verticle") has been successfully deployed:
I'm not entirely sure why the event loop is blocked. You will need to provide additional information so I can try to reproduce this issue. What happens when you send a simple query: |
The connection just closes on me:
And there are no additional logs. I'm on macOS 12.4. Not sure if this helps:
|
Could you please use |
Oh never mind, it works now! (I had forgotten to specify Well, mostly. If I try a mermaid diagram, I get |
Mermaid is provided as a companion container, see: https://docs.kroki.io/kroki/setup/install/#_companion_containers |
I made some local changes and was able to successfully build (and upload to Docker Hub) the gateway server as a Multi-Arch-Image for both arm64 and amd64 — and it deployed successfully on my Raspberry Kubernetes Cluster. Here is a commit I made with all the changes I had to do to make it work. Mainly:
I hope this at least gives those who seek a solution an option to build the stuff themself. I was not able to find anyone who already did this, so I hope this is helpful. |
It works |
@Thomas-Ganter @lidaling I have a PR open (#1487) to build and release both |
Hi @Thomas-Ganter have you ever tested |
@maxsitu There's an open issue #1239 to resolve this, but the maintainer of |
Besides
x68_64
akaamd64
, various ARM platforms are being used for servers or development (Raspberry, Mac, AWS, …). The current docker build process can only build for the developer machine's architecture, typicallyamd64
. This is then also what is published as a docker image on Docker Hub. As a result, ARM servers cannot use the docker image; a complete build system has to be set up on the ARM server before Kroki can be run.Docker supports multi-architecture images seamlessly and efficiently; clients will transparently request the correct image for their architecture, if that architecture is available. For example, Debian base images are available in up to 9 architectures.
If the underlying code runs on multiple architectures as well, then it is easy to build a multi-architecture docker image, e.g., in Knot DNS. If not, these issues need to be sorted out first.
As most of the code is Java, Python, or JavaScript, I would expect the changes to be straightforward.
(Spin-off of #1066 discussion)
The text was updated successfully, but these errors were encountered: