Repository navigation
Strong coupling with "alpine:3.2" image in DockerClientFactory #281
Description
Hello.
When #267 was merged running docker inside docker works fine :) This feature is very useful for CI pipelines when Jenkins slave executes in Docker container, for example.
But build servers may have partial Internet connectivity - to the local Docker registry only (just like in my case). So despite of wonderful docker-in-docker support build fails nevertheless on DockerClientFactory.instance().client() invoke.
Can we get rid of this builtin image dependency or make it customizable at least? For example, pass image name to DockerClientFactory through environment variable?
Activity
bsideup commentedon Jan 24, 2017
Hi @dddpaul,
I suppose #277 will help; we just have to make
TINY_IMAGEconfigurable.Will it work for you? (properties file configuration of the images)
rnorth commentedon Jan 24, 2017
Yes, sorry - I should have remembered to include this in #277
dddpaul commentedon Jan 24, 2017
@bsideup Yes it's will be perfect.
dddpaul commentedon Jan 31, 2017
@bsideup @rnorth Can I help with this issue? I can try to make #277-like PR by myself.
bsideup commentedon Jan 31, 2017
@dddpaul Sure! Fine by me, we're always welcome any contributions :)