Support building securely against remote buildkitd #6732
Comments
aaron-prindle
added
kind/feature-request
area/build
build/docker
priority/p2
|
@vaskozl thanks for the issue, this is an interesting idea. have you tried putting together a prototype using a custom builder? this could be a lower effort way to support this in skaffold without major code changes. we probably won't have the bandwidth to implement this on our end, but if you're interested in putting together a design proposal we would certainly consider accepting a contribution. |
|
This is used in minikube, by running https://github.com/kubernetes/minikube/blob/v1.24.0/pkg/minikube/cruntime/containerd.go#L395 https://github.com/moby/buildkit#containerd-image-store Could also have tunneled a unix socket, but it was too much hassle to set up (together with the other supported runtimes). The workaround is to tar up the build context and scp it... |
|
Keep triage happy |
…Tools#6732) * detect-buildx global config option for backward compatibility * cache-tag global config option to customize cache destination * new CacheTo in DockerArtifact in configuration yaml (for docker build --cache-to) * export LoadDockerConfig to read ~/.docker/config.json for buildx detection * fix avoid loading image via buildx if no docker daemon is accessible * fix remote lookup / import missing in buildx workaround * fix image import if no docker daemon is available (under buildx) * adjust cache reference preserving tag and default cacheTo if not given * parse buildx metadata to extract ImageID digest Initially based on ebekebe's GoogleContainerTools#8172 patch ebekebe@1c1fdeb Signed-off-by: [email protected]
While skaffold supports building against a remote exposed docker, it is also extremely insecure.
https://github.com/moby/buildkit#expose-buildkit-as-a-tcp-service
Buildkitd supports exposing itself directly via mTLS, I currently use
buildctlin my CI to build containers against it quickly.It would be great if skaffold supported building against a remote buildkitd with mTLS.
The text was updated successfully, but these errors were encountered: