Thanks for reporting and pinging us!
I confirm that this timeout error is not related to the Jenkins Kubernetes plugin issue that we face on others Jenkins instances (it’s a VM agent with a Docker Engine in this case).
(The "fabric8" component from the error stack was misleading @Mark ;) ).
We (infra-team) started to check this issue earlier today, and we are on the process to reproduce it.
@Chris, If you have any way to configure the maven-docker plugin to report the equivalent of the commands `docker ps`, `docker logs <moto container ID>` and `docker inspect <moto container ID>` that would be awesome.
Also, if you can try to pull the latest moto image (which is the tag used) and see if it continues working on your environment?
=> On our side we will continue diagnostics tomorrow, by executing the commands on an ephemeral VM based on the same template as ci.jenkins.io
to see if we can reproduce the issue with the exact same tools (same kernel, same Docker, same Maven, same JDK). We’ll keep you updated.