Brent Baude 31a1f44fe6 honor pull policy in play kube ...

When a container specification has a pull policy, we should honor it when recreating the pods/containers from yaml.  furthermore, ini kube, if a tag is :latest, then the always pull policy is automatically instituted.

Fixes: #4880

Signed-off-by: Brent Baude <bbaude@redhat.com>

2020-01-28 13:36:10 -06:00

..

testdata

Split refNamesFromImageReference from Runtime.getPullListFromRef

2018-08-01 18:22:58 +00:00

config.go

honor pull policy in play kube

2020-01-28 13:36:10 -06:00

docker_registry_options.go

pull/create: add --override-arch/--override-os flags

2019-10-29 13:35:19 -04:00

errors.go

add podman container|image exists

2018-11-26 09:19:39 -06:00

filters.go

move image filters under libpod/images

2019-12-10 13:05:18 -06:00

image_test.go

make lint: include unit tests

2020-01-14 10:51:59 +01:00

image.go

inspect image healthchecks

2020-01-27 08:36:25 -06:00

parts_test.go

Remove imageParts.{isTagged,registry,name,tag}

2019-01-14 04:07:24 +01:00

parts.go

honor pull policy in play kube

2020-01-28 13:36:10 -06:00

prune.go

Initial commit on compatible API

2020-01-10 09:41:39 -06:00

pull_test.go

bump containers/image to v5.0.0, buildah to v1.11.4

2019-10-29 13:35:18 -04:00

pull.go

Initial commit on compatible API

2020-01-10 09:41:39 -06:00

search.go

bump containers/image to v5.0.0, buildah to v1.11.4

2019-10-29 13:35:18 -04:00

signing_options.go

Stage3 Image Library

2018-03-14 20:21:31 +00:00

utils.go

images: distinguish between tags and digests

2019-10-29 13:35:19 -04:00