rules_docker loader files no longer accessible from storage.googleapis.com

[zdicesare]

Dependencies in rules_docker like:

https://storage.googleapis.com/rules_docker/aad94363e63d31d574cf701df484b3e8b868a96a/loader-linux-amd64

Defined here

Began to 403 this morning, resulting in inability to build using rules_docker.

Some users still have migrations from rules_docker in progress.

Can this be restored, or is any mirror available?

EDIT by @Wyverald (2025-12-15 10:12 UTC): Temporary access has been restored for 4 weeks, after which they will expire again. Meanwhile, these files have been mirrored to mirror.bazel.build (see #2291 (comment)); to use these updated URLs, use a rules_docker version that contains this commit 0e9c3b0.

[malt3]

Users can help by finding the file in their repsitory cache:

digests=(
    08b8963cce9234f57055bafc7cadd1624cdce3c5990048cea1df453d7d288bc6
    912ee7c469b3e4bf15ba5d1f0ee500e7ec6724518862703fa8b09e4d58ce3ee6
    a5527b7b3b4a266e4680a4ad8939429665d4173f26b35d5d317385134369e438
    4855c4f5927f8fb0f885510ab3e2a166d5fa7cde765fbe9aec97dc6b2761bb22
    5e5ada66beff07f9188bdc1f99c3fa37c407fc0048cd78b9c2047e9c5516f20b
    a80966d17b25dbc9313e9fc1cae74ded5916fa64dba0d33438c8adad338b44d3
    0c0ebc3e0a502542547a38b51f4686a049897eeb4cbc0e2f07fc25276c57866f
    8c9986b2b506febbff737090d9ec485cec1376c52789747573521a85194341c1
)
for f in "${digests[@]}"; do
    ls ~/.cache/bazel/*/cache/repos/v1/content_addressable/sha256/$f/file >/dev/null 2>/dev/null && echo "Found $f" || echo "Missing $f"
done

[ddelnano]

I was able to save the first four files from @malt3's list from my repository cache.

[malt3]

You can upload the files here!

[eightseventhreethree]

I would advise building from source:

bazel build --platforms=@io_bazel_rules_go//go/toolchain:linux_amd64 //container/go/cmd/puller:puller //container/go/cmd/loader:loader

bazel build --platforms=@io_bazel_rules_go//go/toolchain:linux_arm64 //container/go/cmd/puller:puller //container/go/cmd/loader:loader

The files will be in bazel-bin/container/go/cmd/loader/loader_/loader and bazel-bin/container/go/cmd/puller/puller_/puller you'll need to copy out after each build.

[zdicesare]

For completeness, we used the above tips and configured the Bazel downloader like:

rewrite storage.googleapis.com/rules_docker/aad94363e63d31d574cf701df484b3e8b868a96a/(.*) <internal-mirror>/$1

Thank you @malt3 !

[trent-abc]

Same issue for Mac...

https://storage.googleapis.com/rules_docker/aad94363e63d31d574cf701df484b3e8b868a96a/puller-darwin-amd64

[daniel-b2c2]

[Deleted initial fail]

To clarify the steps for building from source I tried and succeeded with are

Clone the repo git clone git@github.com:bazelbuild/rules_docker.git
git checkout ed321b3 (the last tag on github not latest master which has moved on)
Run bazel build --platforms=@io_bazel_rules_go//go/toolchain:linux_amd64 //container/go/cmd/puller:puller //container/go/cmd/loader:loader

I'm unclear on what to do next though

[zdicesare]

[Deleted initial fail]

To clarify the steps for building from source I tried and succeeded with are

Clone the repo git clone git@github.com:bazelbuild/rules_docker.git git checkout ed321b3 (the last tag on github not latest master which has moved on) Run bazel build --platforms=@io_bazel_rules_go//go/toolchain:linux_amd64 //container/go/cmd/puller:puller //container/go/cmd/loader:loader

I'm unclear on what to do next though

this enables you to host the files elsewhere and use a solution like this (blog post)

or apply a patch to the rules_docker ruleset.

[nurus]

I would advise building from source:

bazel build --platforms=@io_bazel_rules_go//go/toolchain:linux_amd64 //container/go/cmd/puller:puller //container/go/cmd/loader:loader

bazel build --platforms=@io_bazel_rules_go//go/toolchain:linux_arm64 //container/go/cmd/puller:puller //container/go/cmd/loader:loader

The files will be in bazel-bin/container/go/cmd/loader/loader_/loader and bazel-bin/container/go/cmd/puller/puller_/puller you'll need to copy out after each build.

I was able to build it and publish it to our internal aftifact host but understandably there's a checksum mismatch. Is the only option to re-package rules_docker with the updated checksum? Ideally if someone could post the missing files with the proper checksums that would be great.

[kulewski]

We were hit by it as well. Luckily, we had one old machine with the cache files. Here is our solution:

0. Never download files strangers post on the Internet. No warranties, etc., etc.
1. Having said that i am attaching the loader loader.tgz files that I extracted from that machine. They work for us. YMMV.
2. Uncompress them to some folder in your workspace, I used repository-overrides:

$ find repository-overrides/
repository-overrides/
repository-overrides/loader
repository-overrides/loader/loader_linux_amd64
repository-overrides/loader/loader_linux_amd64/file
repository-overrides/loader/loader_linux_amd64/file/downloaded
repository-overrides/loader/loader_linux_amd64/file/BUILD
repository-overrides/loader/loader_linux_amd64/WORKSPACE
repository-overrides/loader/loader_linux_s390x
repository-overrides/loader/loader_linux_s390x/file
repository-overrides/loader/loader_linux_s390x/file/downloaded
repository-overrides/loader/loader_linux_s390x/file/BUILD
repository-overrides/loader/loader_linux_s390x/WORKSPACE
repository-overrides/loader/loader_linux_arm64
repository-overrides/loader/loader_linux_arm64/file
repository-overrides/loader/loader_linux_arm64/file/downloaded
repository-overrides/loader/loader_linux_arm64/file/BUILD
repository-overrides/loader/loader_linux_arm64/WORKSPACE
repository-overrides/loader/loader_darwin
repository-overrides/loader/loader_darwin/file
repository-overrides/loader/loader_darwin/file/downloaded
repository-overrides/loader/loader_darwin/file/BUILD
repository-overrides/loader/loader_darwin/WORKSPACE

3. Add to your .bazelrc:

build --override_repository=loader_darwin=repository-overrides/loader/loader_darwin
build --override_repository=loader_linux_amd64=repository-overrides/loader/loader_linux_amd64
build --override_repository=loader_linux_arm64=repository-overrides/loader/loader_linux_arm64
build --override_repository=loader_linux_s390x=repository-overrides/loader/loader_linux_s390x

Enjoy!

[zdicesare]

We were hit by it as well. Luckily, we had one old machine with the cache files. Here is our solution:

0. Never download files strangers post on the Internet. No warranties, etc., etc.
1. Having said that i am attaching the loader loader.tgz files that I extracted from that machine. They work for us. YMMV.
2. Uncompress them to some folder in your workspace, I used repository-overrides:

$ find repository-overrides/
repository-overrides/
repository-overrides/loader
repository-overrides/loader/loader_linux_amd64
repository-overrides/loader/loader_linux_amd64/file
repository-overrides/loader/loader_linux_amd64/file/downloaded
repository-overrides/loader/loader_linux_amd64/file/BUILD
repository-overrides/loader/loader_linux_amd64/WORKSPACE
repository-overrides/loader/loader_linux_s390x
repository-overrides/loader/loader_linux_s390x/file
repository-overrides/loader/loader_linux_s390x/file/downloaded
repository-overrides/loader/loader_linux_s390x/file/BUILD
repository-overrides/loader/loader_linux_s390x/WORKSPACE
repository-overrides/loader/loader_linux_arm64
repository-overrides/loader/loader_linux_arm64/file
repository-overrides/loader/loader_linux_arm64/file/downloaded
repository-overrides/loader/loader_linux_arm64/file/BUILD
repository-overrides/loader/loader_linux_arm64/WORKSPACE
repository-overrides/loader/loader_darwin
repository-overrides/loader/loader_darwin/file
repository-overrides/loader/loader_darwin/file/downloaded
repository-overrides/loader/loader_darwin/file/BUILD
repository-overrides/loader/loader_darwin/WORKSPACE

3. Add to your .bazelrc:

build --override_repository=loader_darwin=repository-overrides/loader/loader_darwin
build --override_repository=loader_linux_amd64=repository-overrides/loader/loader_linux_amd64
build --override_repository=loader_linux_arm64=repository-overrides/loader/loader_linux_arm64
build --override_repository=loader_linux_s390x=repository-overrides/loader/loader_linux_s390x

Enjoy!

Users can also verify that the sha256sum of any files files they obtain match the digests in rules_docker

[ttahir86]

what we did was

1. clone repo git clone https://github.com/bazelbuild/rules_docker.git
2. navigate into repo
3. run git checkout v0.25.0
4. Build relevant targets, for us that was bazel build --platforms=@io_bazel_rules_go//go/toolchain:linux_amd64 //container/go/cmd/puller:puller //container/go/cmd/loader:loader
5. navigate to output dir where binaries are placed bazel-bin/container/go/cmd/puller/puller_/
6. Calculate sha256 of both binaries and take note of them sha256sum loader and sha256sum puller
7. host these binaries somewhere, ex gcp storage, s3, etc.
8. if using workspace, update your workspace to override pulling the target from its original source to the one you created and hosted
9. example:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_file")

http_file(
    name = "go_puller_linux_amd64",
    downloaded_file_path = "downloaded", # this needs to be downloaded because rules docker is looking for this in a specific location
    executable = True,
    sha256 = "somesha",  # the sha calculated from step 7
    urls = ["https://where-you-hosted-your-binaries/my-bazel-binaries/puller-linux-amd64"],
)

http_file(
    name = "go_loader_linux_amd64",
    downloaded_file_path = "downloaded",  # this needs to be downloaded because rules docker is looking for this in a specific location
    executable = True,
    sha256 = "somesha",  # the sha calculated from step 7loader
    urls = ["https://where-you-hosted-your-binaries/my-bazel-binaries/loader-linux-amd64"],
)

Note that the above should be before any container_repositories() or container_deps() calls to properly override.

thats it.

[kulewski]

Also, for us the same happened to puller files.

I am attaching them as well puller.tgz

repository-overrides/puller
repository-overrides/puller/go_puller_linux_amd64
repository-overrides/puller/go_puller_linux_amd64/file
repository-overrides/puller/go_puller_linux_amd64/file/downloaded
repository-overrides/puller/go_puller_linux_amd64/file/BUILD
repository-overrides/puller/go_puller_linux_amd64/WORKSPACE
repository-overrides/puller/go_puller_darwin
repository-overrides/puller/go_puller_darwin/file
repository-overrides/puller/go_puller_darwin/file/downloaded
repository-overrides/puller/go_puller_darwin/file/BUILD
repository-overrides/puller/go_puller_darwin/WORKSPACE
repository-overrides/puller/go_puller_linux_s390x
repository-overrides/puller/go_puller_linux_s390x/file
repository-overrides/puller/go_puller_linux_s390x/file/downloaded
repository-overrides/puller/go_puller_linux_s390x/file/BUILD
repository-overrides/puller/go_puller_linux_s390x/WORKSPACE
repository-overrides/puller/go_puller_linux_arm64
repository-overrides/puller/go_puller_linux_arm64/file
repository-overrides/puller/go_puller_linux_arm64/file/downloaded
repository-overrides/puller/go_puller_linux_arm64/file/BUILD
repository-overrides/puller/go_puller_linux_arm64/WORKSPACE

.bazelrc

build --override_repository=go_puller_darwin=repository-overrides/puller/go_puller_darwin
build --override_repository=go_puller_linux_amd64=repository-overrides/puller/go_puller_linux_amd64
build --override_repository=go_puller_linux_arm64=repository-overrides/puller/go_puller_linux_arm64
build --override_repository=go_puller_linux_s390x=repository-overrides/puller/go_puller_linux_s390x

[nurus]

Thanks so much @kulewski! Those binaries with the expected shas is just what I needed. I can just upload them to our artifact repository and use re-write rules and avoid having to checking this into our source code.

[tyler-french]

Can we upload these to https://mirror.bazel.build/?