docker-build-ami
Build Amazon EC2 AMI image using a Dockerfile
Limitations
Only supports instructions ENV, RUN, COPY and ADD, other instructions will just be ignored.
Configuration
There is a separate config file for the script in either “/etc/docker-build-ami.conf” or “~/.docker-build-ami.conf”.
# Temporary directory
# tmp_dir = /tmp
# Name tag for host building AMI image
# host_tag = docker-build-ami
# Region
# region = eu-west-1
# Instance type
# instance_type = m3.medium
# Subnet ID
# subnet_id = subnet-123abc45
# AWS access key id
# aws_access_key_id = DFSDF3HGDF4SDSD1DDFF
# AWS secret access key
# aws_secret_access_key = 3riljdsf5SDFSDvsdfds452sdSDFDfsdf44SDFdR
Usage
usage: docker-build-ami [-h] [-c CONFIG] [-d] [-r] [-t] [-s] [-n] [-i] [-u]
optional arguments:
-h, --help show this help message and exit
-c CONFIG, --config CONFIG
Configuration file
-d, --debug Print debug info
-r, --region AWS region
-t, --instance-type EC2 instance type
-s, --subnet-id AWS subnet id
-n, --image-name Target AMI image name
-i, --image-id Source AMI image ID
-u, --image-user AMI image user
Metadata
Release files for docker-build-ami 0.3.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| docker-build-ami-0.3.7.tar.gz | 5.5 kB | Without provenance | Details for docker-build-ami-0.3.7.tar.gz |
Release files / docker-build-ami-0.3.7.tar.gz
| Download URL | docker-build-ami-0.3.7.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
21bfacb1110d24926e7c8f1d702ae3309809909fc0cb51ce8d6975971ab13e83
|
|
BLAKE2b-256 checksum How to use checksums |
46c5b3942e150f60e139feae421f0db1c160fa45bacb12f5c6d221bf829c3b40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for docker-build-ami 0.3.7
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.