Matthew Heon c6255537d9 Fix a potential segfault in podman search ...

When generating headers for search, we unconditionally
access element 0 of an array, and I saw this segfault in our CI.
There's no reason we have to do this, we're just going through it
to get field names with reflect, so just make a new copy of the
struct in question.

Also, move this code, which is only for CLI display, into
cmd/podman from libpod/image.

Signed-off-by: Matthew Heon <mheon@redhat.com>

2019-04-03 15:11:08 -04: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

Changes to container runlabel for toolbox project

2019-01-30 08:44:58 -06:00

image.go

Set blob cache directory based on GraphDriver

2019-03-29 08:27:33 -04:00

parts_test.go

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

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

parts.go

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

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

prune.go

Add event logging to libpod, even display to podman

2019-03-11 15:08:59 -05:00

pull_test.go

Use imageParts.referenceWithRegistry in pullGoalFromPossiblyUnqualifiedName

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

pull.go

Set blob cache directory based on GraphDriver

2019-03-29 08:27:33 -04:00

search.go

Fix a potential segfault in podman search

2019-04-03 15:11:08 -04:00

signing_options.go

Stage3 Image Library

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

utils.go

podman-remote save [image]

2019-02-20 12:58:05 -06:00