Can you expand a bit on why you'd like to do that vs the other options?
One of the downsides of the "we create our own docker images" plan is that
we have to maintain them. How do you want to do that?
to be clear: I'm asking because I'm trying to figure out what the community
wants and right
Agree it's what I said in a previous email.
Regards
JB
On Apr 10, 2017, 18:58, at 18:58, Ekrem Aksoy wrote:
>Hi Stephen,
>
>Can we piggyback on current Apache Docker Hub account? I think images
>can
>be hold there, too.
>
>-E
>
>On Mon, Apr 10, 2017 at 5:22 PM, Stephen
Hi Stephen,
Can we piggyback on current Apache Docker Hub account? I think images can
be hold there, too.
-E
On Mon, Apr 10, 2017 at 5:22 PM, Stephen Sisk
wrote:
> for 4 - there's a number of logistics involved. How do you propose handling
> cost, potential DOS, etc?
for 4 - there's a number of logistics involved. How do you propose handling
cost, potential DOS, etc? People in different timezones would need to be
oncall for it since it impacts people's ability to dev work (or they need
to be okay if it goes out.) Can you give some reasons why you think it's
+1
> On Apr 7, 2017, at 10:46 PM, Jean-Baptiste Onofré wrote:
>
> Hi Stephen,
>
> I think we should go to 1 and 4:
>
> 1. Try to use existing images providing what we need. If we don't find
> existing image, we can always ask and help other community to provide so.
> 4. If
Hi Stephen,
I think we should go to 1 and 4:
1. Try to use existing images providing what we need. If we don't find existing
image, we can always ask and help other community to provide so.
4. If we don't find a suitable image, and waiting for this image, we can store
the image in our own "IT
I'd like to hear what direction folks want to go in, and from there look at
the options. I think for some of these options (like running our own public
registry), they may be able to and it's something we should look at, but I
don't assume they have time to work on this type of issue.
S
On Tue,
Summary:
For IO ITs that use data stores that need custom docker images in order to
run, we can't currently use them in a kubernetes cluster (which is where we
host our data stores.) I have a couple options for how to solve this and am
looking for feedback from folks involved in creating IO