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”.
# [main]
# 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
# Security Groups
# security_group_ids = ["sg-1234", "sg-23456"]
# Host Tags - additional tags to add to EC2 host
# host_tags = [{"Key": "foo", "Value": "bar"}]
# AWS access key id
# aws_access_key_id = DFSDF3HGDF4SDSD1DDFF
# AWS secret access key
# aws_secret_access_key = 3riljdsf5SDFSDvsdfds452sdSDFDfsdf44SDFdRA
# Base image from which the output image is built
# image_id = ami-0df67e2624dedbae1
# EC2 user used to build instances (usually AMI dependent)
# image_user = ubuntu
# The AMI Name of the output image
# image_name = ubuntu-test
# Image Tags - tags to add to AMI
# image_tags = [{"Key": "foo", "Value": "bar"}]
Usage
usage: docker-build-ami [-h] [-c CONFIG] [-d] [-r REGION] [-t INSTANCE_TYPE]
[-s SUBNET_ID] [-n IMAGE_NAME] [-i IMAGE_ID]
[-u IMAGE_USER]
optional arguments:
-h, --help show this help message and exit
-c CONFIG, --config CONFIG
Configuration file
-d, --debug Print debug info
-r REGION, --region REGION
AWS region
-t INSTANCE_TYPE, --instance-type INSTANCE_TYPE
EC2 instance type
-s SUBNET_ID, --subnet-id SUBNET_ID
AWS subnet id
-n IMAGE_NAME, --image-name IMAGE_NAME
Target AMI image name
-i IMAGE_ID, --image-id IMAGE_ID
Source AMI image ID
-u IMAGE_USER, --image-user IMAGE_USER
AMI image user
Running Tests
# Run these lines once
pip3 install -r requirements-test.txt
pre-commit install
# Run these lines to check code formatting and correctness
flake8 --show-source --filename="\*.py" .
pytest --cov=docker2ami
Metadata
Release files for mmuller88-docker-build-ami 0.7.6
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 |
|---|---|---|---|---|
| mmuller88-docker-build-ami-0.7.6.tar.gz | 10.8 kB | Without provenance | Details for mmuller88-docker-build-ami-0.7.6.tar.gz |
Release files / mmuller88-docker-build-ami-0.7.6.tar.gz
| Download URL | mmuller88-docker-build-ami-0.7.6.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bef852a4194c22d7d508550f112b9c9f0f4c1d31d44cdb1d402bb12448f406d6
|
|
BLAKE2b-256 checksum How to use checksums |
af79202133b672ac3fe5dbde250581bf53d53b05a97ee18cd12dd941739d4e35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.6.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.61.2 CPython/3.9.6
|
Security for mmuller88-docker-build-ami 0.7.6
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.