Build Runs Every Time Despite Using Remote Cache

We are doing the following on CI:

```
bazel build //... \
--remote_cache=https://storage.googleapis.com/ \
--google_default_credentials
```

We have a build target that uses rules docker that bazel runs every time, despite using the remote cache. It does not depend on other targets in our application, except for ones that are rarely modified. Is this expected behavior? It's not completely clear to me whether this is a bug. Any guidance on a workaround or otherwise would be appreciated. Unfortunately, the docker build target is expensive, as it involves compilation of third-party sources. We are looking at sharding the build on CI to multiple machines due to this issue.