composerisation
A CLI tool used to convert between docker-compose to normal Docker CLI commands.
Warning: This project is still in beta.
Demo
Instead of dowloading the tool you can use the demo website. Simply paste your docker-compose.yml file and press convert then copy the contents from the second input box.
Warning: The website is only for demo purposes, the code isn’t particularly clean. This is not a web service but a CLI tool
Usage
pip install composerisation
composerisation --helpUsage: composerisation [OPTIONS]
Converts docker-compose files to Docker comamnds.
- Options:
- -i, --input-file TEXT
Path to file to convert from docker-compose to Docker. [required]
- -l, --log-level
[DEBUG|INFO|ERROR|CRITICAL] Log level for the script.
- --help
Show this message and exit
$ composerisation -i docker-compose.ymlDocker
You can also use the docker image to convert between docker-compose and Docker cli.
docker run -v ${PWD}/tests/data/1.yml:/app/docker-compose.yml composerisationSupported Command
We support all commands specified in the docker-compose reference file version 3.8 here. Besides from the config options defined below.
Services
Unsupported config options:
configs
credential_spec
depends_on
deploy
external_links
healthcheck
secrets
volume (long syntax)
Networks
Unsupported config options:
enable_ipv6
Future Features
Convert between Docker cli commands to docker-compose
Add docker pull, when using images
Changelog
You can find the changelog here.
Appendix
1 maintainer
Metadata
1 maintainer
Release files for composerisation 0.1.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 | |
|---|---|---|---|---|
| composerisation-0.1.2.tar.gz | 13.3 kB | Without provenance | Details |
Release files / composerisation-0.1.2.tar.gz
| Download URL | composerisation-0.1.2.tar.gz |
|---|---|
| Size | 13.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c4d146a3623dd9ebd3386bf1c5d7993c25879d7b8c3189325a4db527cb3f4447
|
|
BLAKE2b-256 checksum How to use checksums |
52bb6895103bf606756d38d5ab0df9ad05f7565dee2e687158d4bc34371b2525
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.7.3 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.6.13
|
Security for composerisation 0.1.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.
