That’s the move, IMO.
That said, there are a fair amount of legacy deployments still kicking
around. For reference, every time a security patch is released somebody
pings our docker repo within a few days. So folks are using it and watching
for releases.
Providing the community with some examples
create pull
> requests. If you like, you can even add the complete docker/kubernetes
> part as pull request.
> If you have any questions, don't hesitate to ask.
>
> Regards
>
> Martin
>
>
> Am Samstag, 20. Oktober 2018, 01:30:41 CEST schrieb Terence Kent:
> >
; good idea, if the file is downloaded dynamically during container
> start/build.
>
> Regards
>
> Martin
>
> Am Freitag, 19. Oktober 2018, 02:08:52 CEST schrieb Terence Kent:
> > Hello,
> >
> > In early 2015, we made our Archiva docker image public. It's ha
Stefaan, Matthew,
I hate "works for me responses", so apologies in advance. However, we are
seeing artifacts automatically removed according to our repository
retention settings in our deployment and I wanted to share
possibly-relevant information.
We've been using Archiva version 2.2.3 in a dock
Hello,
In early 2015, we made our Archiva docker image public. It's had a small
following on github/dockerhub and we field questions on it from time to
time. As best we can tell, it's the de-facto docker image for Archiva.
We recently moved to Kubernetes and were faced with the decision of
droppi
