rules_docker
rules_docker copied to clipboard
Rules for building and handling Docker images with Bazel
Is this supported? ``` # WORKSPACE container_pull( name = "envoyproxy-distroless", digest = "sha256:319ae2f7889c0ca395da53ca835e04aa09fe2bff23f4fab962853b9d68129bf2", # v1.22-latest registry = "index.docker.io", repository = "envoyproxy/envoy-distroless", ) container_pull( name = "openjdk", digest = "sha256:e81b7f317654b0f26d3993e014b04bcb29250339b11b9de41e130feecd4cd43c", #...
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more. ## Awaiting Schedule These updates are awaiting their schedule. Click on a checkbox to...
This has always been done in `push.bzl` (via `push-tag.sh.tpl`). Just making `push-all.bzl` consistent. ## PR Checklist Please check if your PR fulfills the following requirements: - [ ] Tests for...
# 🐞 bug report ### Affected Rule `container_load` ### Is this a regression? No, it's arguable whether this is even a bug rather than a feature. I experienced it as...
Currently the go_image target always uses an amd64 base image even when goarch is provided by the user This can be partially worked-around by specifying a base image properly using...
## PR Checklist Please check if your PR fulfills the following requirements: - [ ] Tests for the changes have been added (for bug fixes / features) - [ ]...
# 🐞 bug report ### Affected Rule The issue is caused by the rule: container_push ### Is this a regression? Yes, the previous version in which this bug was not...
## PR Checklist Please check if your PR fulfills the following requirements: - [ ] Tests for the changes have been added (for bug fixes / features) - [x] Docs...
# 🚀 feature request ### Relevant Rules [`container_push`](https://github.com/bazelbuild/rules_docker/blob/master/docs/container.md#container_push) ### Description `container_push` is a bit of an odd duck. The README [suggests using bazel stamping](https://github.com/bazelbuild/rules_docker#stamping) or [`--define` flags](https://github.com/bazelbuild/rules_docker#make-variables) to vary where...
Just like `cmd` but for `run`. This would be really cool, because it would allow for implementing aspects of docker files in bazel instead of having to resort to use...