start session: connect buildkit session: unexpected status 500: incompatible client | Dagger | Page 1

wise marten Nov 27, 2025, 4:07 PM

#

Hi, I was playing with the argo workflows on Kubernetes (on Ubuntu 24.04 LTS).
Since I updated local and dagger-helm to latest v0.19.7, it seems the minikube cluster namespace remains on previous client version and breaks on buildkit session connect 👀

➜ dagger-module docker container list --all --filter 'name=^dagger-engine-*' --format '{{.Names}}'
dagger-engine-v0.19.7

https://docs.dagger.io/getting-started/ci-integrations/argo-workflows/
https://docs.dagger.io/reference/deployment/kubernetes/#prerequisites

Tried the troubleshooting to remove the dagger namespace/containers but in vain...
https://docs.dagger.io/reference/troubleshooting/#dagger-is-unresponsive-with-a-buildkit-error

PS: dagger checks are OK 🙂

➜ dagger-module dagger checks
✔ Module.checks: CheckGroup! 0.0s
✔ .run: CheckGroup! 0.0s
✔ .list: [Check!]! 0.0s

Thanks for your feedback.

wise marten Nov 27, 2025, 4:45 PM

#

Found only this topic by searching for similar error...

#1354070922713366631 message

sour copper Nov 27, 2025, 5:03 PM

#

@wise marten seems like you have a very old dagger client?

sour copper Nov 27, 2025, 5:04 PM

#

wise marten Hi, I was playing with the argo workflows on Kubernetes (on Ubuntu 24.04 LTS). S...

The message that you see in this image is because the client seems to be quite outdated. What do you get if you run dagger version

#

Is it possible that you have multiple dagger binaries in your system in different paths?

wise marten Nov 27, 2025, 6:30 PM

#

sour copper Is it possible that you have multiple dagger binaries in your system in differen...

Hi, here is the version I have :

➜ ~ whereis dagger
dagger: /usr/local/bin/dagger $HOME/.local/bin/dagger $HOME/bin/dagger
➜ ~ dagger version
dagger v0.19.7 (image://registry.dagger.io/engine:v0.19.7) linux/amd64

#

Otherwise, here is my cluster state having helm.sh/chart: dagger-helm-0.19.7

wise marten Nov 27, 2025, 7:14 PM

#

What I have when running Dagger shell, It seems having also trouble connecting...

sour copper Nov 27, 2025, 9:20 PM

#

wise marten Otherwise, here is my cluster state having `helm.sh/chart: dagger-helm-0.19.7`

Can you verify that your cluster engine pod is effectively using the v0.19.7 image?

#

Is that the case?

wise marten Nov 27, 2025, 9:34 PM

#

Well, it occurs that I had to simply relaunch my terminal (Ghostty) to have the right dagger version applied, was testing the dagger query in a terminal not referencing the latest dagger version after update...
Now it's ok, don't see why the terminal didn't updated 🤷‍♂️

wise marten Nov 27, 2025, 9:52 PM

#

Setting the DAGGER_CLOUD_TOKEN environment variable is only necessary if integrating with Dagger Cloud.

Just to check : It says optional but keeps the Pod in CreateContainerConfigError state. Do we have to provide any token anyway ? 🤔

  # assumes the Dagger Cloud token is
  # in a Kubernetes secret named dagger-cloud
- name: "DAGGER_CLOUD_TOKEN"
  valueFrom:
    secretKeyRef:
      name: dagger-cloud
      key: token

Name: dagger-in-argo-98c4c
Namespace: argo
ServiceAccount: unset (will run with the default ServiceAccount)
Status: Running
Conditions:
PodRunning False
Created: Thu Nov 27 22:45:43 +0100 (4 minutes ago)
Started: Thu Nov 27 22:45:43 +0100 (4 minutes ago)
Duration: 4 minutes 15 seconds
Progress: 0/1

STEP TEMPLATE PODNAME DURATION MESSAGE
◷ dagger-in-argo-98c4c dagger-workflow dagger-in-argo-98c4c 4m CreateContainerConfigError: secret "dagger-cloud" not found

#start session: connect buildkit session: unexpected status 500: incompatible client