Fabric8io docker-maven plugin runs on pipeline only from inside a bash script

[Judith Owens]

We use the fabric8io docker-maven plugin to manage docker image building within our project, and while it runs fine locally when we use it on Pipelines we get the following:

Downloaded from central: https://repo.maven.apache.org/maven2/com/google/guava/guava/23.0-android/guava-23.0-android.jar (2.5 MB at 2.4 MB/s)
[ERROR] DOCKER> Cannot create docker access object  [Connect to localhost:2375 [localhost/127.0.0.1] failed: Connection refused (Connection refused)]

[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.31.0:build (default-cli) on project parent: Cannot create docker access object : Connect to localhost:2375 [localhost/127.0.0.1] failed: Connection refused (Connection refused) -> [Help 1]

 However, we *only* get that error if we use the plugin directly, ie by including a step of:

    mvn docker:build

If we have the same command inside a bash script and get Pipelines to call the bash script as a step, the plugin build succeeds.

I've tried looking at env both as a step and inside the bash script to compare, and in both cases the only difference is sub-shell layer. Running env also appears to cause the plugin to start failing even from inside a bash script.

Any thoughts?

Edit: Since the env tests, that branch (and only that branch) is now failing even if the plugin is called from inside a script.

[Judith Owens]

Okay folks, I'm an eejit - it helps if one remembers that the reason it worked from the bash script on one step was because that was the one where you had the Docker service set up...!