docker: Problem with 3.x images and dependencies?

[rdmueller]

somehow, the 3.x docker images are slower than the 2.x ones when used in a closed environment pipeline.

the image uses some tricks to make itself selfcontained: https://github.com/docToolchain/docker-image/blob/ng-beta/alpine/Dockerfile#L45

but this seems not to work anymore. I get the feeling that the image runs in timeouts because it tries to download dependencies but has no connection to the internet from within the pipeline.

[PacoVK]

Could you please check if the issue is still there in 3.3.1? :)

[rdmueller]

3.3.1 still needs external dependencies. This is how I test it:

run the image:

docker run -it doctoolchain/doctoolchain:v3.3.1

then execute the following commands

curl -Lo dtcw https://doctoolchain.org/dtcw 
chmod +x dtcw

turn off wifi and execute

./dtcw local generateSite --info

this returns the following error

* Where:
Build file '/home/dtcuser/docToolchain/build.gradle' line: 26

* What went wrong:
Plugin [id: 'org.aim42.htmlSanityCheck', version: '1.1.6'] was not found in any of the following sources:

- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (could not resolve plugin artifact 
'org.aim42.htmlSanityCheck:org.aim42.htmlSanityCheck.gradle.plugin:1.1.6')
 Searched in the following repositories:
 Gradle Central Plugin Repository

[PacoVK]

Hey @rdmueller i think the issue is the usage of the doctoolchain image rather than a bug. I can reproduce the behaviour using the steps you described, but i can also proof this is not a bug when using the image as intended (maybe we lack some documentation here) Let me shed some light in here:

• using the image with the steps you described and downloading dtcw (again) but in the local project folder, let's the wrapper set the default runtime and gradle cache directory (/home/dtcuser/.doctoolchain/.gradle/) This directory is empty, because all the dependencies have been installed in another local (global) Gradle cache dir /home/dtcuser/.gradle/. This is exactly why you see this error. In fact we enforce another cache dir in the wrapper that is different from what we set when building the image and predownloading all dependencies (see) --> i don't know yet, whether this may just be some old stuff that we should get rid of, tbh

• if you would just omit the steps of downloading another dtcw-wrapper, but instead the existing predefined doctoolchain installation it works as expected even in offline mode. (we add doctoolchain into the PATH inside the container on image creation see) and here

Let me outline the steps to follow to make it work:

Run the image (+ mount a volume with asciidocfiles)

docker run -it doctoolchain/doctoolchain:v3.3.1

turn off wifi and execute, mind . is the context where your project should be located

doctoolchain . generateSite --info

Can you please verify, i guess we do not actually need to fix the dependency resolution any further, as far as i can see. But we should check if there is documentation missing.