rules_docker
github.com
Spec sheet
- Purpose
- rules_docker is a set of Bazel rules for pulling base images, adding build artifacts and assets, and publishing container images.Read 4 Oct 2026 · github.com
- License
- The repository is licensed under Apache License 2.0.Read 4 Oct 2026 · github.com
- Container operations
- Basic rules include container_image, container_bundle, container_import, container_load, container_pull, and container_push.Read 4 Oct 2026 · github.com
- Docker dependency
- The basic image pull, build, and push rules do not require or use Docker.Read 4 Oct 2026 · github.com
- Language rules
- The project provides image rules for Python, Node.js, Java, Scala, Groovy, C++, Go, Rust, and D.Read 4 Oct 2026 · github.com
- Maintenance
- The repository says rules_docker is maintained on an as-needed basis and points users to rules_oci as an alternative.Read 4 Oct 2026 · github.com
- Notable limitation
- The README says language image rules do not expose Docker-related attributes, so adding a custom environment variable or symlink requires using a container_image target.Read 4 Oct 2026 · github.com
- Package and run rules
- Additional rules can install apt-get packages and run commands inside containers, but they require a properly configured Docker binary.Read 4 Oct 2026 · github.com
- Platform support
- The README says the rules can be used on OSX without boot2docker or docker-machine, while Windows use is not supported.Read 4 Oct 2026 · github.com
- Registry integration
- container_pull and container_push use google/go-containerregistry for registry interactions, and the README describes standard Docker authentication for private images.Read 4 Oct 2026 · github.com
- Reproducibility
- The repository says images produced by container_image are deterministic and reproducible.Read 4 Oct 2026 · github.com
- Runtime base
- Higher-level language image rules use distroless language runtimes by default, with a configurable base attribute.Read 4 Oct 2026 · github.com
- Security reporting
- The security policy directs vulnerability reports to Google's g.co/vulnz intake and says the Google Security Team processes reports within a day and responds within a week, depending on severity.Read 4 Oct 2026 · github.com
- Workstation access
- The README says these rules do not require root access on the workstation.Read 4 Oct 2026 · github.com
Plans and prices
rules_docker Free Apache-2.0 · maintained on an as-needed basis · Windows is not supported Read 4 Oct 2026 · github.com
Where Specifiction places it
- Container Build Tools#26 of 347.3