You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is a bug or FR, but the documentation is at least a tiny bit contradicting. From the docu, I would expect that the only limitation I get when using the tar driver is the missing support for commandTests. See this section:
tar: a tar driver, which extracts an image filesystem to wherever tests are running, and runs file/metadata tests against it. Does not support command tests.
The example in that same section shows how it works providing a image:tag (not a *.tar file!)
container-structure-test test --driver tar --image gcr.io/registry/image:latest --config config.yaml
Workaround: use oci_tarball. I thought this rule is only used as a bazel run target to load the tarball into your docker daemon, but it turns out to also provide a tarball 🎉
Not sure if this is a bug or FR, but the documentation is at least a tiny bit contradicting. From the docu, I would expect that the only limitation I get when using the
tar
driver is the missing support forcommandTests
. See this section:The example in that same section shows how it works providing a
image:tag
(not a*.tar
file!)container-structure-test test --driver tar --image gcr.io/registry/image:latest --config config.yaml
When using the
tar
driver in bazelit fails with
Error in fail: when the 'driver' attribute is not 'docker', then the image must be a .tar file
SOURCESo is this a real limitation? The tool itself apparently is happy to consume
image:tag
combos 🤔If so, what is the canonical way to use the
tar
driver withrules_oci
?The text was updated successfully, but these errors were encountered: