docker_builder

Docker Builder

Build script to create containers, tag them and push them to a remote repository.

Install

pip install docker-builder

Usage

docker-builder [-f <builder.yaml>] [--no-push] [--no-cache] [<container>...]

Config file

It expects a config file in yaml format in the current folder named builder.yaml.

Format

registries:
  - registry: https://index.docker.io/v1/
    username: user
    password: pass
    email: email

  - registry: local
    username: 127.0.0.1:5000

containers:
  - container1
  - container2
  - container3

Registries

Each of the containers will be tagged and pushed to each of the registries with the latest tag.

If registry is local, no login will be attempted and the container will be pushed to the local registry as defined in the username. If registry is an http/https based registry, the username, password and email will be used to login.

Containers

The containers attribute defines a list of containers and the order in which they will be built. It effectively defines the dependencies among containers and ensure the “source” ones are built first.

Each of the containers defined in the list must be defined in a matching name folder.

Metadata

Release files for docker_builder 0.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for docker_builder 0.2
File	Size	Uploaded	Provenance
docker_builder-0.2.tar.gz	3.9 kB	Jan 22, 2015	Without provenance	Details

Release files / docker_builder-0.2.tar.gz

Download URL	docker_builder-0.2.tar.gz
Size	3.9 kB
Tags	Source
SHA-256 checksum How to use checksums	`82ec7cd4a2f877646931333fbad7230ba990cdc872b6c5d3f06b91e8be29dbcb`
BLAKE2b-256 checksum How to use checksums	`216617757ec3cd8535f926ca3908ade5cd4e7294478edb695fcefd83cb2d30f1`
Upload date	Jan 22, 2015
Uploaded using Trusted Publishing? What is trusted publishing?	No

Security for docker_builder 0.2

Report project as malware

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.