Looks like triggering the pipeline manually somehow got it working. Seems to be related to the fact that on the second run it uses the cached docker image.
2018-05-19 20:22 GMT+02:00 Dominik Psenner <dpsen...@gmail.com>: > Hi, > > I observe more failures of the log4net pipeline, caused by an exception > when invoking the docker command: > > docker build -t efc862d2a5aded416b465a4d4f3dddc0e8f6ee25 -f > buildtools/docker/builder-mono-2.0/Dockerfile > buildtools/docker/builder-mono-2.0 > > > The exception is: > > java.io.IOException: Cannot retrieve .Id from 'docker inspect ubuntu:16.04' > at > org.jenkinsci.plugins.docker.workflow.client.DockerClient.inspectRequiredField(DockerClient.java:220) > at > org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:133) > at > org.jenkinsci.plugins.docker.workflow.FromFingerprintStep$Execution.run(FromFingerprintStep.java:85) > > > Does anyone know what this is about or what I could do to remedy the > problem? The full build log can be examined at > https://builds.apache.org/job/logging-log4net/job/feature% > 252Fcd-pipeline/234/consoleFull . > > Cheers > -- > Dominik Psenner > -- Dominik Psenner
