Engine error on k8s cluster | Dagger | Page 1

helm upgrade --install --namespace=dagger --create-namespace \
    dagger oci://registry.dagger.io/dagger-helm

DAGGER_ENGINE_POD_NAME="$(kubectl get pod \
    --selector=name=dagger-dagger-helm-engine --namespace=dagger \
    --output=jsonpath='{.items[0].metadata.name}')"
export DAGGER_ENGINE_POD_NAME

_EXPERIMENTAL_DAGGER_RUNNER_HOST="kube-pod://$DAGGER_ENGINE_POD_NAME?namespace=dagger"
export _EXPERIMENTAL_DAGGER_RUNNER_HOST

dagger query <<EOF
{
    container {
        from(address:"alpine") {
            withExec(args: ["uname", "-a"]) { stdout }
        }
    }
}
EOF

✘ connect 10.9s
! start engine: new client: interrupted
│ ✔ starting engine 0.0s
│ ✘ connecting to engine 10.9s
│ ! new client: interrupted
│ │ ✘ moby.buildkit.v1.Control/Info 3.0s
│ │ ! connection error: desc = "error reading server preface: read |0: file already closed"
│ │ ✘ moby.buildkit.v1.Control/Info 0.0s
│ │ ! connection error: desc = "error reading server preface: read |0: file already closed"
│ │ ✘ moby.buildkit.v1.Control/Info 0.0s
│ │ ! connection error: desc = "error reading server preface: read |0: file already closed"
│ │ ✘ moby.buildkit.v1.Control/Info 0.0s
│ │ ! connection error: desc = "error reading server preface: read |0: file already closed"
│ │ ✘ moby.buildkit.v1.Control/Info 0.0s
│ │ ! connection error: desc = "error reading server preface: read |0: file already closed"
│ │ ✘ moby.buildkit.v1.Control/Info 0.0s

#Engine error on k8s cluster