bazel container image rules

We have hosted the application bazel container image rules in order to run this application in our online workstations with Wine or directly.

Quick description about bazel container image rules:

This repository contains a set of rules for pulling down base images, augmenting them with build artifacts and assets, and publishing those images. These rules do not require / use Docker for pulling, building, or pushing images. These rules used to be docker_build, docker_push, etc. and the aliases for these (mostly) legacy names still exist largely for backwards-compatibility. We also have early-stage oci_image, oci_push, etc. aliases for folks that enjoy the consistency of a consistent rule prefix. The only place the format-specific names currently do any more than alias things is in foo_push, where they also specify the appropriate format as which to publish the image. They can be used to develop Docker containers on OSX without boot2docker or docker-machine installed. Note use of these rules on Windows is currently not supported. Also, unlike traditional container builds (e.g. Dockerfile), the Docker images produced by container_image are deterministic / reproducible.

Features:

• Generated API documentation is in the docs folder
• In addition to low-level rules for building containers, this repository provides a set of higher-level rules for containerizing applications
• Use with Docker locally
• You can use these rules to access private images using standard Docker authentication methods
• Varying image names
• For Python and Java's lang_image rules, you can factor dependencies that don't change into their own layers

Programming Language: Go.
Categories: