Hi, • I am testing

ImageSpec

on sandbox. • I tried to follow the instructions from PR #1001 and PR #3860. However, it still failed to build and push the docker images to the sandbox docker registry. • So what would be the pre-requisite and necessary steps to configure ImageSpec for sandbox registry? Thanks

(flyte) ➜  test_case git:(main) ✗ kubectl -n flyte get deployments.apps
NAME                                 READY   UP-TO-DATE   AVAILABLE   AGE
flyte-sandbox-kubernetes-dashboard   1/1     1            1           8d
flyte-sandbox-proxy                  1/1     1            1           8d
flyte-sandbox-minio                  1/1     1            1           8d
flyte-sandbox-docker-registry        1/1     1            1           8d
flyte-sandbox                        1/1     1            1           8d
(flyte) ➜  test_case git:(main) ✗ pip freeze | grep flytekit
flytekit==1.8.2
flytekitplugins-envd==1.8.2

I haven’t added buikkdkit deployment to the latest release yet. you can use this sandbox image instead.

flytectl demo start --image=<http://ghcr.io/flyteorg/flyte-sandbox-bundled:sha-713f3f86a4d74d555e1a55b52065119df39117e3|ghcr.io/flyteorg/flyte-sandbox-bundled:sha-713f3f86a4d74d555e1a55b52065119df39117e3>

https://flyte-org.slack.com/archives/CP2HDHKE1/p1690846410170349?thread_ts=1690561576.249449&cid=CP2HDHKE1

Thanks, @Kevin Su. Now it works. • So basically we can ignore the steps described in PR #1001, right? These steps seem to configure the local docker container of

buildkit

, while it still cannot reach the network of k3s cluster. • The latest solution is to include

buildkit

into the k3s sandbox cluster. And we just need to follow the steps in PR #3860 to create the envd context and configure the python file.

yes, correct

@Kevin Su Can we use ImageSpec on workflow level? If we choose to use ImageSpect, do we have to add the

container_image

keyword before each of the task? If we do not specify

container_image

to some of the tasks, would they use a default image?

Can we use ImageSpec on workflow level

we don’t support that.

If we do not specify

container_image

to some of the tasks, would they use a default image?

yes, it will use default image. flyteorg/flytekit:latest

Thanks, Kevin.