[ 
https://issues.apache.org/jira/browse/JCLOUDS-1021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966523#comment-14966523
 ] 

Josef Cacek edited comment on JCLOUDS-1021 at 10/21/15 9:27 AM:
----------------------------------------------------------------

Digging deeper in the code, I've found I was wrong about stating it's always 
emtpy. It's empty when retrieved from the {{ImageApi}} call. Nevertheless, the 
method 
{{org.jclouds.docker.compute.strategy.DockerComputeServiceAdapter.listImages()}}
 recreates the {{Image}} instance and fills the {{repoTags}} field with the 
missing info retrieved from {{ImageApi.listImages}} method.

IMO, It could be sufficient to cover the behavior in the JavaDoc (e.g. for 
ImageApi.inspectImage() method).


was (Author: kwart):
Digging deeper in the code, I've found I was wrong about stating it's always 
emtpy. It's empty when retrieved from the {{ImageApi}} call. Nevertheless, the 
method 
{{org.jclouds.docker.compute.strategy.DockerComputeServiceAdapter.listImages()}}
 recreates the {{Image}} instance and fills the {{repoTags}} field with the 
missing info retrieved from {{ImageApi.listImages}} method.

> Remove repoTags field from org.jclouds.docker.domain.Image
> ----------------------------------------------------------
>
>                 Key: JCLOUDS-1021
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1021
>             Project: jclouds
>          Issue Type: Bug
>    Affects Versions: 1.9.1
>            Reporter: Josef Cacek
>              Labels: docker-lab
>
> The {{org.jclouds.docker.domain.Image}} class contains {{repoTags}} field, 
> but it's always empty. The {{ImageApi.inspectImage()}} method which returns 
> {{Image}} instances doesn't retrieve info about the tags. 
> User can retrieve tags by using {{ImageApi.listImages()}} method which 
> returns {{List<ImageSummary>}}. The {{ImageSummary}} instances correctly 
> contain the tag information.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to