Daniel J Walsh a6046dceef Remove the ability to use [name:tag] in podman load command ... Docker does not support this, and it is confusing what to do if the image has more then one tag. We are dropping support for this in podman 3.0 Fixes: https://github.com/containers/podman/issues/7387 Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>		2021-01-12 17:38:32 -05:00
..
containers.go	Include named volumes in container migration	2021-01-07 07:51:19 +00:00
containers_create.go	Switch all references to github.com/containers/libpod -> podman	2020-07-28 08:23:45 -04:00
containers_stats.go	Lowercase some errors	2020-10-05 15:56:44 -07:00
copy.go	Switch all references to github.com/containers/libpod -> podman	2020-07-28 08:23:45 -04:00
generate.go	generate kube on multiple containers	2020-12-07 11:34:39 -06:00
healthcheck.go	Switch all references to github.com/containers/libpod -> podman	2020-07-28 08:23:45 -04:00
images.go	Remove the ability to use [name:tag] in podman load command	2021-01-12 17:38:32 -05:00
images_pull.go	libpod API: pull: fix channel race	2021-01-04 17:46:24 +01:00
info.go	Switch all references to github.com/containers/libpod -> podman	2020-07-28 08:23:45 -04:00
manifests.go	fix allowing inspect manifest of non-local image	2020-09-30 14:12:32 -04:00
networks.go	podman network label support	2020-11-28 18:35:43 +01:00
play.go	Add an option to control if play kube should start the pod	2020-11-17 20:00:58 +01:00
pods.go	Use abi PodPs implementation for libpod/pods/json endpoint	2021-01-09 23:38:26 +01:00
swagger.go	Switch all references to github.com/containers/libpod -> podman	2020-07-28 08:23:45 -04:00
system.go	Restore compatible API for prune endpoints	2021-01-07 15:32:32 -07:00
volumes.go	Rework pruning to report reclaimed space	2020-12-30 19:57:35 -06:00