summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authoralsadi <alsadi@gmail.com>2019-04-21 15:53:37 +0300
committeralsadi <alsadi@gmail.com>2019-04-25 11:42:50 +0300
commitc17b931a79aebabb38daba033a09230d3866b088 (patch)
tree671bb662c5a977173a316084eb2cfe09496bd047
parentb01fdcbbd5344e89c3d9f3462c1df1764277d9fd (diff)
downloadpodman-c17b931a79aebabb38daba033a09230d3866b088.tar.gz
podman-c17b931a79aebabb38daba033a09230d3866b088.tar.bz2
podman-c17b931a79aebabb38daba033a09230d3866b088.zip
point to 3rd party tools for `docker-compose` format
Signed-off-by: alsadi <alsadi@gmail.com>
-rw-r--r--README.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/README.md b/README.md
index 73a7057ea..da516fa0d 100644
--- a/README.md
+++ b/README.md
@@ -45,7 +45,11 @@ This project tests all builds against each supported version of Fedora, the late
Podman can also generate Kubernetes YAML based on a container or Pod (see
[podman-generate-kube](https://github.com/containers/libpod/blob/master/docs/podman-generate-kube.1.md)),
which allows for an easy transition from a local development environment
- to a production Kubernetes cluster.
+ to a production Kubernetes cluster. If Kubernetes does not fit your requirements,
+ there are other third-party tools that support the docker-compose format such as
+ [kompose](https://github.com/kubernetes/kompose/) and
+ [podman-compose](https://github.com/muayyad-alsadi/podman-compose)
+ that might be appropriate for your environment.
## OCI Projects Plans