[FEATURE]: ARM64 support for the garden CLI
See original GitHub issueFeature Request
Hi! I would love to be able to use garden from my low power ARM64 based laptop.
Background / Motivation
I work on a fairly heavyweight project, a web service backed by multiple docker containers running java apps, but Iβd love to be able to work from a low power machine without being tied to a large workstation all day.
What should the user be able to do?
Install and use garden CLI on ARM64 hardware, connected to a cluster of any architecture (most likely x86_64)
Why do they want to do this? What problem does it solve?
See motivation above.
Suggested Implementation(s)
I have tried to simply remove the check in src/core/garden.ts
and building according to the instructions in CONTRIBUTING.md. This results in a usable garden
executable being built. When I try to initialize a remote cluster to use with garden however, I get an error
Sample garden.yml, just the basic example. k8s cluster is running on my x86_64 workstation, and kubectl is connected correctly.
kind: Project
name: phr
environments:
- name: dev
providers:
- name: kubernetes
context: k3d-k3s-default
defaultEnvironment: dev
Sample error
[martin@martin-pinebook phr]$ garden --env=dev plugins kubernetes cluster-init
Plugins
Initializing/updating cluster-wide services for dev environment
βΉ providers β Getting status...
Failed resolving provider container. Here is the output:
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Command docker doesn't have a spec for this platform/architecture (linux-arm64)
ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Failed resolving one or more providers:
- container
See error.log for detailed error message
providers β Getting status...
How important is this feature for you/your team?
πΉ Itβs a nice to have, but nice things are nice π
Issue Analytics
- State:
- Created 2 years ago
- Comments:19 (1 by maintainers)
Just a quick update, we are on a path to do this. A little tricky because it involves several updates to 3rd party tools we use, but weβll get there soon.
@MFAshby If you start a pull request, I can try and help.