Zack Zeng

> port-forwarding may consume many API server CPUs. Would you mind elaborating? AFAIK if there is no much traffic, port-forwarding should not consume too much cpu resources, as it is...

> + config.working_dir(local=".", remote="https://github.com/tensorchord/envd.git") My concern is that working dir seems to be a command line argument to me, otherwise it might prevent the reuse of `build.envd` in different working...

Perhaps we could make `MIDI` work in a way similar to `docker-buildx`, which uses the BuildKit library bundled into the Docker daemon with docker driver, so that the image is...

> 7GB image load takes ~17s Wow! It is really awsome! 💯

I dived a little deeper into buildx and I am sure that `docker load` is not necessarily required by `buildx`. Excerpt from the official documentaion: https://docs.docker.com/engine/reference/commandline/buildx_create/#driver > **docker driver** >...

> I am wondering why we should use docker 20.10.14, is it the version that supports built-in load? Nope, it is just the version of the dockerd in my laptop.....

> working dir mount I think we could not mount local dir to container in k8s cluster directly, how about we spawn a rsyncd inside the container, and sync working...

> We rely on LocalDirs in SolveOpt to expose cache dir to the build process. The LocalDirs is not supported in build func. We should make cache dir a llb.Local,...

Please correct me if I missing something 🤔, we cannot access dir outside the build context dir during build time if envd is used as a buildkit frontend since buildx...

> I think the client in controller-runtime wraps client-go a lot and it should be easier to use. @gaocegege Yeah the client provided by `controller-runtime` is a general one and...