Nicolas Lopez

I think this can be closed as rules_docker now has an alternative solution for this issue (https://github.com/bazelbuild/rules_docker/issues/379)

I do think it makes sense to print some form of progress message for these long running actions. My one concern is wrt how to print out these messages (i.e.,...

This sounds like a valid use case, but I don't know enough yet about how container registry works to know if its feasible/simple to do this. Maybe @mattmoor or @dlorenc...

It sounds like the work needed to get this use case supported is mostly related to making the script in this repo work with contents that are in the CAS....

About option iii: It should be feasible to provide a way to push with rules_docker using `bazel build`. wrt authentication, please see https://github.com/bazelbuild/rules_docker/issues/526 for an open thread to provide better...

hi @lberk , I am doing some work related to this, but it's not likely I will extend the scope to cover fixing this specific issue. Details of my current...

Apologies, just noticed your error is not related to containerregistry (which was my initial thought as its the source of most of my issues related to python). We will soon...

hi @strican and @mishudark, thanks for creating this issue, and sorry for the delay responding. We are not currently working on supporting mac builds for these rules. We would, nevertheless,...

`--action_env=BAZEL_DO_NOT_DETECT_CPP_TOOLCHAIN=1` cannot be used with `--incompatible_enable_cc_toolchain_resolution`. I was running some additional tests with `--incompatible_enable_cc_toolchain_resolution` with RBE (although this does not have to do with RBE, I think), and I was...

Hi Marcel, You can repro this error using as base [this GCB build script](https://github.com/bazelbuild/bazel-toolchains/blob/master/tests/rbe_repo/bazel_incompatible_0_25.yaml) which tests a very simple cc target (`//examples/remotebuildexecution/hello_world/cc:say_hello_test`, i.e., I am not building the `cc_toolchain_target`) The...