Dockerize will pack up your dynamically linked ELF binaries and all
their dependencies and turn them into a Docker image.
Some example images built with this tool are available from:
- https://hub.docker.com/u/dockerizeme/
## Synopsis
usage: dockerize [-h] [--tag TAG] [--cmd CMD] [--entrypoint ENTRYPOINT]
[--no-build] [--output-dir OUTPUT_DIR] [--add-file SRC DST]
[--user USER] [--group GROUP] [--filetools] [--verbose]
[--debug]
...
positional arguments:
paths
optional arguments:
-h, --help show this help message and exit
--add-file SRC DST, -a SRC DST
Add file <src> to image at <dst>
--user USER, -u USER Add user to /etc/passwd in image
--group GROUP, -g GROUP
Add group to /etc/group in image
--filetools Add common file manipulation tools
Docker options:
--tag TAG, -t TAG Tag to apply to Docker image
--cmd CMD, -c CMD
--entrypoint ENTRYPOINT, -e ENTRYPOINT
Output options:
--no-build, -n Do not build Docker image
--output-dir OUTPUT_DIR, -o OUTPUT_DIR
Logging options:
--verbose
--debug
## A simple example
Create a `sed` image:
dockerize -t sed /bin/sed
Use it:
$ echo hello world | docker run -i sed s/world/jupiter
hello jupiter
## A more complicated example
Create an image named `thttpd`:
dockerize -t thttpd \
-a /var/www/thttpd /var/www \
--entrypoint '/usr/sbin/thttpd -D' \
--cmd '-d /var/www' \
/usr/sbin/thttpd
Serve default content:
docker run thttpd
Serve your own content:
docker run -v /my/content:/var/www thttpd
Metadata
Release files for dockerize 0.2.2
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 | |
|---|---|---|---|---|
| dockerize-0.2.2.tar.gz | 19.0 kB | Without provenance | Details |
Release files / dockerize-0.2.2.tar.gz
| Download URL | dockerize-0.2.2.tar.gz |
|---|---|
| Size | 19.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
efd705bb6c2dd6e516c42c083530ba1d014fd10a9733fb0972fddc3adfb9567f
|
|
BLAKE2b-256 checksum How to use checksums |
a26d17b5566f2fad5f904c8bd8b1ddc6599c5fd156bc5a761a176ff880f02d78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for dockerize 0.2.2
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.