#Custom `BUILDKIT_HOST` no more supported ?

1 messages Β· Page 1 of 1 (latest)

drifting wyvern
#

Naive question : dagger doesn't support using BUILDKIT_HOST anymore ? It used to work in previous version, it doesn't seem to be the case anymore. What would be the alternative ?

sand fern
#

Have you tried it in that way?
_EXPERIMENTAL_DAGGER_RUNNER_HOST=docker-container://buildkit-dagger

I used that to connect to our internal artifactory.

drifting wyvern
#

oh.. πŸ˜„

#

(intersting, with podman-container it.. is stuck πŸ™ƒ )

sand fern
#

Ok. We don't use podman.

drifting wyvern
#

Yeah, I'll have to dig into why it fails, but thanks for the env var, that's what I was looking for

#

I wonder if it's an artifact from "old days" and using podman-container is not supported in that env var

#

(cc @crisp swift πŸ˜› )

verbal yarrow
drifting wyvern
#

oh I realize my mistake now πŸ˜…

#

thanks @verbal yarrow, a typo 😬

crisp swift
#

Note that we don’t support external buildkitd anymore.

drifting wyvern
#

all goes through the engine image now if I understood correctly

crisp swift
#

yes correct

drifting wyvern
#

so it still work in "custom" setup (with podman & co), just not directly on a buildkit socket that wouldn't be managed by the engine

#

πŸ‘

#

make sense πŸ™‚