summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorValentin Rothberg <rothberg@redhat.com>2020-02-13 14:27:47 +0100
committerValentin Rothberg <rothberg@redhat.com>2020-02-13 14:28:58 +0100
commitf8443eb83af941efbfbb2b302c013e8235d13ef4 (patch)
tree38c642f55ee2955528da1dddf081c8ef0f15b5a4 /README.md
parent2814995a9281b3b8e67d7c48df28de0de742b995 (diff)
downloadpodman-f8443eb83af941efbfbb2b302c013e8235d13ef4.tar.gz
podman-f8443eb83af941efbfbb2b302c013e8235d13ef4.tar.bz2
podman-f8443eb83af941efbfbb2b302c013e8235d13ef4.zip
README: fix docs links
Fix: #5106 Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index 4fbe2ecea..950602e0a 100644
--- a/README.md
+++ b/README.md
@@ -73,9 +73,9 @@ A little configuration by an administrator is required before rootless Podman ca
standard for composing Pods and for orchestrating containers, making
Kubernetes YAML a defacto standard file format. Hence, Podman allows the
creation and execution of Pods from a Kubernetes YAML file (see
- [podman-play-kube](https://github.com/containers/libpod/blob/master/docs/podman-play-kube.1.md)).
+ [podman-play-kube](https://github.com/containers/libpod/blob/master/docs/source/markdown/podman-play-kube.1.md)).
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)),
+ [podman-generate-kube](https://github.com/containers/libpod/blob/master/docs/source/markdown/podman-generate-kube.1.md)),
which allows for an easy transition from a local development environment
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