[heketi-devel] heketi docker images

[Raghavendra Talur]

On Thu, Nov 3, 2016 at 6:43 PM, Mohamed Ashiq Liyazudeen
<mliyazud at redhat.com> wrote:
> Hi,
>
> In deploy-heketi-deployment.json and heketi-deployment.json, We make use of heketi/heketi:latest image whose build has failed(https://hub.docker.com/r/heketi/heketi/builds/). heketi/heketi:latest is 22 days old, but heketi/heketi:3 is 14 days old (so latest is not actually latest). Someone should keep track of the builds. We also have container image with tags 3 and 2 so we should be using these images in the release branches respectively.

We can debug this together.

>
> I think using heketi/gluster should be avoided and we should start using gluster/gluster-centos. Why should heketi maintain a separate gluster container image? I feel this will be overhead in future. If we have any specific changes to be added to gluster/gluster-centos, we can raise a bug. What do you guys think?

+1 gluster images should be sourced from gluster/ owner.

>
> I think one more person (other than Luis) should have access to docker hub[1], so that there is no bottleneck (in case of build re-trigger, ignore if this has already been taken care of).

Michael?

>
> [1] https://hub.docker.com/u/heketi/
>
> --
> Regards,
> Mohamed Ashiq.L
> _______________________________________________
> heketi-devel mailing list
> heketi-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/heketi-devel