Docker containers for more platforms
See original GitHub issueBesides x68_64
aka amd64
, 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, typically amd64
. 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)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top GitHub Comments
Mermaid is provided as a companion container, see: https://docs.kroki.io/kroki/setup/install/#_companion_containers
Oh never mind, it works now! (I had forgotten to specify
HTTP/1.1
in my telnet command)Well, mostly. If I try a mermaid diagram, I get
Error 503: Connection refused: /127.0.0.1:8002