3:48 a.m.
Folks,
I recently started to look at jboss/wildfly
<https://registry.hub.docker.com/u/jboss/wildfly/> and noticed that this does not
use tags. As a consequence, any image that build of jboss/wildfly is subject to breakage
when there is an update of this repo. I suggest to also provide tagged versions of these
images similar to this
<https://registry.hub.docker.com/u/tdiesler/wildfly/tags/manage/>;.
cheers
—thomas
5:09 a.m.
Tracked by: https://issues.jboss.org/browse/WFLY-3996
<https://issues.jboss.org/browse/WFLY-3996>
On 20 Oct 2014, at 10:48, Thomas Diesler <tdiesler(a)redhat.com>
wrote:
Folks,
I recently started to look at jboss/wildfly
<https://registry.hub.docker.com/u/jboss/wildfly/> and noticed that this does not
use tags. As a consequence, any image that build of jboss/wildfly is subject to breakage
when there is an update of this repo. I suggest to also provide tagged versions of these
images similar to this
<https://registry.hub.docker.com/u/tdiesler/wildfly/tags/manage/>;.
cheers
—thomas
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
8:09 a.m.
// Resending to all
Thomas,
It was not possible to use tags in the previous set up where we had all
our dockerfiles in one repository. Now I'm in the process of moving
them to their own repos under: https://github.com/jboss-dockerfiles/
Tags will be added at some point (the lack of tags triggered the move,
btw).
--Marek
On pon, paź 20, 2014 at 10:48 , Thomas Diesler <tdiesler(a)redhat.com>
wrote:
Folks,
I recently started to look at jboss/wildfly and noticed that this
does not use tags. As a consequence, any image that build of
jboss/wildfly is subject to breakage when there is an update of this
repo. I suggest to also provide tagged versions of these images
similar to this.
cheers
—thomas
3705
days inactive
3705
days old
2 comments
2 participants
participants (2)
-
Marek Goldmann -
Thomas Diesler