hey trying to use `ImageSpec` on the hello world example the

Question

hey trying to use `ImageSpec` on the hello world example the hello world file ```from flytekit import ImageSpec task workflow image = ImageSpec name= imagespec registry= localhost 30000 packages= smart open gcs apt packages= git task container image=image def say hello gt str return hello world workflow def my wf gt str return say hello ``` I am running the demo sandbox and executed this ```cd ~ projects flytesnacks examples basics flytectl demo start envd context use name flyte sandbox``` Using the right context I think ``` envd context ls CONTEXT BUILDER BUILDER ADDR RUNNER RUNNER ADDR default docker container docker flyte sandbox current tcp docker``` Getting this error ``` pyflyte run remote basics hello world py my wf Image localhost 30000 imagespec smnRYWZ9xTB4xFoEmprU Q not found Building Run command envd build path tmp flyte 7hnhtddt sandbox local flytekit 9759c0608f0326822a33edc8a8603f11 platform linux amd64 output type=image name=localhost 30000 imagespec smnRYWZ9xTB4xFoEmprU Q push=true Failed with Unknown Exception lt class Exception gt Reason failed to run command envd build path tmp flyte 7hnhtddt sandbox local flytekit 9759c0608f0326822a33edc8a8603f11 platform linux amd64 output type=image name=localhost 30000 imagespec smnRYWZ9xTB4xFoEmprU Q push=true with error b error timeout 5s cannot connect to buildkitd n failed to run command envd build path tmp flyte 7hnhtddt sandbox local flytekit 9759c0608f0326822a33edc8a8603f11 platform linux amd64 output type=image name=localhost 30000 imagespec smnRYWZ9xTB4xFoEmprU Q push=true with error b error timeout 5s cannot connect to buildkitd n ```

Kevin Su · Answer

is builtkit deployment running

Kevin Su · Answer

you can check it by running `kubectl get pods n flyte`

Kevin Su · Answer

```registry= localhost 30000``` should use 30003 here

Hud · Answer

Hey < Kevin Su> changing to 30003 didn t solve it ``` kubectl get pods n flyte NAME READY STATUS RESTARTS AGE flyte sandbox kubernetes dashboard 6757db879c 8kbm2 1 1 Running 0 72s flyte sandbox proxy d95874857 zlc2k 1 1 Running 0 72s flyte sandbox docker registry 67b7b67664 89zlh 1 1 Running 0 72s flyte sandbox minio 645c8ddf7c mj6dt 1 1 Running 0 72s flyte sandbox postgresql 0 1 1 Running 0 73s flyte sandbox 98749fb56 p5dc6 1 1 Running 0 72s``` doesn t seem like the builtkit is running how can I start this

Hud · Answer

< Kevin Su> wondering if you had an idea how to resolve this

Kevin Su · Answer

cc < jeev> did we add buildkit deployment to the latest sandbox image

jeev · Answer

< Kevin Su> unreleased

jeev · Answer

```flytectl demo start image=<http ghcr io flyteorg flyte sandbox bundled sha 713f3f86a4d74d555e1a55b52065119df39117e3|ghcr io flyteorg flyte sandbox bundled sha 713f3f86a4d74d555e1a55b52065119df39117e3>``` to use the latest nightly image ``` gt kubectl get po A NAMESPACE NAME READY STATUS RESTARTS AGE flyte flyte sandbox postgresql 0 1 1 Running 0 59s flyte flyte sandbox proxy d95874857 6l52x 1 1 Running 0 59s kube system local path provisioner 7b7dc8d6f5 sjlfr 1 1 Running 0 59s flyte flyte sandbox docker registry 5876748b9c tg482 1 1 Running 0 59s kube system coredns b96499967 rv99h 1 1 Running 0 59s flyte flyte sandbox kubernetes dashboard 6757db879c smvr6 1 1 Running 0 59s flyte flyte sandbox minio 645c8ddf7c 2tv64 1 1 Running 0 59s flyte flyte sandbox buildkit 7d7d55dbb mgpk6 1 1 Running 0 59s kube system metrics server 668d979685 nv7r9 1 1 Running 0 59s flyte flyte sandbox 98749fb56 xxq9n 1 1 Running 1 37s ago 59s```

jeev · Answer

or whatever `flyteorg flyte` commit after the buildkit commit went in

jeev · Answer

format is ```flytectl demo start image=<http ghcr io flyteorg flyte sandbox bundled sha lt LONG COMMIT|ghcr io flyteorg flyte sandbox bundled sha lt LONG COMMIT> gt ```

Hud · Answer

works