Miloslav Trmač a6e668fac5 Don't call image.DecomposeString in imageInListToContainerImage ...

- It is used to fill Repository(misnamed)/Tag members which have no users;
  so it's completely unclear why this is useful.
- Given the mishandling of tags by imageParts.tag, at the very least
  all new code should primarily use reference.Named (even if
  after a decompose() to internally deal with unqualified names first),
  introducing new uses of original decompose() just reintroduces known
  trouble - so without any provided rationale, reverting seems
  a reasonable default action.
- This drags in all of libpod/image into the "remote client" build,
  which seems undesirable.

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

2019-01-14 03:55:44 +01:00

..

client.go

Add ability to build golang remote client

2019-01-07 12:43:57 -06:00

images_remote.go

remote-client support for images

2019-01-10 13:18:08 -06:00

info_remote.go

Add ability to build golang remote client

2019-01-07 12:43:57 -06:00

runtime_remote.go

Don't call image.DecomposeString in imageInListToContainerImage

2019-01-14 03:55:44 +01:00

runtime.go

remote-client support for images

2019-01-10 13:18:08 -06:00