Miloslav Trmač b9c0f2c987 Use reference.TagNameOnly instead of manually adding imageParts.tag in normalizeTag ...

Again, rely on the official API, instead of the suprising "suspiciousTagValueForSearch"
value (set to :latest on untagged images, and :none on digested ones!)

CHANGES BEHAVIOR, but the previous output of normalization of digested values was
not even syntatically valid, so this can't really be worse.

Still, maybe we should refuse to tag with digested references in the first place.

Signed-off-by: Miloslav Trmač <mitr@redhat.com>

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

..

testdata

Split refNamesFromImageReference from Runtime.getPullListFromRef

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

docker_registry_options.go

Minimally update for the DockerInsecureSkipTLSVerify type change

2018-12-06 23:34:59 +01:00

errors.go

add podman container|image exists

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

image_test.go

Use reference.TagNameOnly instead of manually adding imageParts.tag in normalizeTag

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

image.go

Use reference.TagNameOnly instead of manually adding imageParts.tag in normalizeTag

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

parts_test.go

Add imageParts.normalizedReference()

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

parts.go

Add imageParts.normalizedReference()

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

prune.go

Add ability to prune containers and images

2018-12-05 19:57:54 -06:00

pull_test.go

Use imageParts.referenceWithRegistry in pullGoalFromPossiblyUnqualifiedName

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

pull.go

Use getPullRefPair / getSinglePullRefPairGoal in pullGoalFromPossiblyUnqualifiedName

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

signing_options.go

Stage3 Image Library

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

utils.go

Drop image.DecomposeString, make image.Parts private imageParts again

2019-01-14 04:06:58 +01:00