Unable to install Dagster via HELM
See original GitHub issueI am trying to install Dagster via HELM on AWS EKS by following this documentation: https://docs.dagster.io/deployment/guides/kubernetes/deploying-with-helm
I am using EKS version 1.23 and the Dagster HELM chart version 1.0.12
I install dagster and then get the following errors, but I’m not sure why this is happening.
All three pods have one failed container: Daemon -
Dagit -
Dagster user deployments -
The error log in all the Daemon and Dagit failed containers is:
exec /bin/bash: exec format error
The error log in the user deployment container is:
exec /usr/local/bin/dagster: exec format error
I am not sure as to what the problem could be given that I am following the tutorial. Is it an EKS / HELM incompatibility issue?
Issue Analytics
- State:
- Created a year ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Deploying with Helm - Dagster Docs
Using Helm, users specify the configuration of required Kubernetes resources to deploy Dagster through a values file or command-line overrides.
Read more >Deploying with Helm - Dagster Docs
We walk through a Kubernetes deployment of Dagster using Helm. ... If you are creating your own user code images, Docker should be...
Read more >Customizing your Kubernetes Deployment - Dagster Docs
This section covers common ways to customize your Dagster Helm deployment. ... to pass custom configuration through to the Kubernetes Jobs and Pods...
Read more >Customizing Helm - Dagster Docs
We go over common ways to customize your Dagster Helm deployment. This includes adding Kubernetes and Celery configuration at the pipeline and solid...
Read more >dagster-k8s API docs
Configuration set using tags on a @job will only apply to the run level. ... Upon installation, the Helm chart will provide instructions...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@madhur-tandon You are right 😃 My EC2 instances were of type “g” which are ARM based, and the official Dagster images are built on AMD architectures. Switching to type “a” EC2 solved it for me. I am closing this issue.
It’s probably because you guys are building the docker image on an M1 Mac i.e. ARM architecture while the EC2 machines on the EKS cluster are Linux machines with the x86 or perhaps amd64 architecture. You should probably use the
--platform
argument while building your image with docker.