spiegel_podman/pkg/bindings
Alban Bedel 7ab936eafa Add an option to control if play kube should start the pod
Having play kube start the pod is not always appropriate, one might
for example like to have the pod running as a set of systemd services.
Add a `start` option to the command line and API to control if the pod
should be started or not; it defaults to true for backward
compatibility.

Signed-off-by: Alban Bedel <albeu@free.fr>
2020-11-17 20:00:58 +01:00
..
containers Stop binding layer from changing line endings 2020-11-09 10:37:18 -07:00
generate APIv2 add generate systemd endpoint 2020-09-02 22:06:19 +02:00
images Podman-remote build is getting ID twice 2020-11-14 06:25:29 -05:00
manifests Switch all references to github.com/containers/libpod -> podman 2020-07-28 08:23:45 -04:00
network Fix network remove for the podman remote client 2020-09-28 13:34:56 +02:00
play Add an option to control if play kube should start the pod 2020-11-17 20:00:58 +01:00
pods Switch all references to github.com/containers/libpod -> podman 2020-07-28 08:23:45 -04:00
system Refactor version handling in cmd tree 2020-09-18 15:13:58 -07:00
test move from docker.io 2020-10-28 13:16:37 -06:00
volumes Switch all references to github.com/containers/libpod -> podman 2020-07-28 08:23:45 -04:00
bindings.go Refactor version handling in cmd tree 2020-09-18 15:13:58 -07:00
connection.go Add support for host keys for non-22 ports 2020-10-25 16:30:42 +01:00
errors.go Switch all references to github.com/containers/libpod -> podman 2020-07-28 08:23:45 -04:00