I'm about to implement support for the 'container-image' platform property to Buildbarn. The idea is to patch the input root with the whole content of the container image. We realised that maybe Bazel should do that instead.
Implementing it in Bazel would require a rule to download the container and list the content, possibly done remotely. Another variant is to build a container using rules_docker and then specify that as 'container-image' in a toolchain and/or platform. When running remote-execution, then all the files in the container would be listed in the input root (making the Merkle tree calculation slow unless caching).
Is this in the scope for what Bazel should be doing or should we just stick to the current 'container-image' platform property instead?
Best regards,
Fredrik