rules_img
github.com
- Free plan
- macOS
- Linux
- Self-hosted
7.1 Club score Visit github.com
What the maker publishes
- Bazel setups
- It supports both Bzlmod and WORKSPACE setups. source
- Bazel support
- It supports both Bzlmod and WORKSPACE setups. source
- Builds
- It builds standard OCI images without requiring a Docker daemon and describes its builds as fully hermetic. source
- Builds
- The project describes its builds as hermetic and says they require no Docker daemon. source
- Container runtimes
- Its image loading rules support Docker, Podman, and containerd. source
- Container runtimes
- The documentation describes loading images into Docker, containerd, and Podman, among other supported targets. source
- Image registries
- Its rules can pull base images from and push images to container registries. source
- Image signing
- Image signing is configurable and disabled by default; the project documents signing plugins and signing workflows. source
- Intended users
- The project describes its push strategies as designed for organizations with thousands of builds per day. source
- Layer efficiency
- It can represent layers as compact streams and reconstruct full layer tar files on demand at push or load time. source
- Lazy pulling
- It supports eStargz and SOCI for lazy pulling optimization. source
- Lazy pulling
- It supports eStargz and SOCI for lazy pulling container images. source
- License
- The repository identifies its license as Apache-2.0. source
- Multi-platform
- It supports multi-platform image builds through Bazel transitions. source
- Multi-platform images
- It supports multi-platform images through Bazel transitions, with examples for linux/amd64 and linux/arm64. source
- OCI compatibility
- It builds standard OCI images compatible with container runtimes. source
- Purpose
- rules_img provides Bazel rules for building OCI container images with performance optimizations. source
- Purpose
- rules_img provides Bazel rules for building OCI container images with performance optimizations. source
- Push strategy limits
- The CAS push strategy requires a special registry and Bazel remote cache, while the BES strategy requires a self-hosted BES server, a special backend, and a Bazel remote cache. source
- Registry authentication
- For registry authentication, it documents Bazel credential helpers, environment credentials, Docker or Podman configuration, Google credentials, and Amazon ECR credentials. source
- Registry authentication
- It documents credential helpers, Docker and Podman configuration, Google credentials, and Amazon ECR credentials for registry access. source
- Registry integrations
- It documents integration with Docker Hub, Google Artifact Registry, Amazon ECR, Harbor, and JFrog Artifactory, with feature support varying by registry. source
- Remote builds
- It integrates with Remote Build Execution and Content Addressable Storage, and can push layers from the remote execution cluster to a registry at build time. source
- Remote execution
- The project describes integration with Remote Build Execution and Content Addressable Storage. source
Checked against the maker's pages on 9 Oct 2026.