Where's toolchain_configure?

[grepwood]

I'm one of those users who use a pre-installed Docker toolchain, as described here: https://github.com/bazelbuild/rules_docker/blob/3040e1fd74659a52d1cdaff81359f57ee0e2bb41/README.md?plain=1#L127

My setup relies on a certain vendor injecting the Docker version they see fit in their product. I would like to not stray away from their solution, because when they find out that my Bazel code tries to run its own show with its own Docker binary, they may try to discount all of their responsibility if something tangentially related to Docker doesn't work in my setup, and shift the responsibility for this on me.

Where can I find the settings to configure the Docker toolchain in rules_oci or anything else that will completely eliminate this behavior?

rules_oci/README.md

Line 27 in bf4c60b

- Use our toolchain hermetically: don't assume there is a docker pre-installed on the machine.

[thesayyn]

rules_oci does not have docker dependency, therefore does need a docker toolchain.

[grepwood]

I'm reading https://docs.aspect.build/guides/rules_oci_migration/ and I see that a lot of functions are already covered by rules_oci. How come rules_oci skips the requirement for an adequate toolchain?

[thesayyn]

I am not sure where the requirements come from, nowhere in rules_oci we depend on docker executable, everything we depend on is brought by a hermetic toolchain, eg: crane, regctl.

With the expection of oci_load;

originally oci_load did not depend on the host docker client, we just told people to use bazel build :tarball and do docker load -i bazel-bin/pth/tarball.tar

However people wanted a convenient way to do bazel build :oci_tarball | docker load so we made oci_load runnable which does exactly this.

[loeffel-io]

but how to use crane in v2.0.1? @thesayyn

[thesayyn]

We didn't change anything about crane. it's same as before.