Intermittent Docker isssue Running mvn verify locally

[tsande16]

Environment

The issue was realized in a local development environment on a Windows 11 machine.

Date/time occurred

This issue started around mid December 2024.

Description

When running mvn verify on pass-support, there will be an intermittent issue with docker that will interrupt the build process and fail to complete the whole mvn verify process. It happens at various points of the build process. Two documented modules where it happens is during the pass-journal-loader-nih , nihms-token-refresh, and nihms-docker module.

Steps to Reproduce

Run mvn verify. The issue will occur intermittently so it may take a couple runs before the error presents itself. More often than not, cleaning out the images and volumes and then restarting docker will stop this error for happening, but it will return on another run.

Expected Results

A successful mvn verify

Actual Results

What occurs is a the error message: [ERROR] DOCKER> Cannot create docker access object [\\.\pipe\docker_engine (All pipe instances are busy)]

Evidence

During the nihms-token-refresh submodule

[INFO] 
[INFO] --- docker:0.45.1:build (build-nihms-docker-image) @ nihms-docker ---
[ERROR] DOCKER> Cannot create docker access object  [\\.\pipe\docker_engine (All pipe instances are busy)]

---

During the nihms-docker module verify, in particular the build-nihms-docker-image exection

[INFO] 
[INFO] --- docker:0.45.1:build (build-nihms-docker-image) @ nihms-docker ---
[ERROR] DOCKER> Cannot create docker access object  [\\.\pipe\docker_engine (All pipe instances are busy)]

---

During the pass-journal-loader-nih

[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 17.34 s -- in org.eclipse.pass.loader.journal.nih.DepositIT
[INFO] 
[INFO] Results:
[INFO] 
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[INFO] 
[INFO] 
[INFO] --- docker:0.45.1:build (build-after-its) @ pass-journal-loader-nih ---
[ERROR] DOCKER> Cannot create docker access object  [\\.\pipe\docker_engine (All pipe instances are busy)]

---

Commenting out io.fabric8 in pass-journal-loader-nih

Commenting out the plugin in the pass-journal-loader-nih will prevent the image from being built and allow the verify process to continue.

However, keeping the plugin uncommented, but only running verify on the pass-journal-loader-nih module, will allow it to pass

Commenting out io.fabric8 docker-maven-plugin in pass-journal-loader-nih, nihms-docker , and nihms-token-refresh

Commenting out the io.fabric8 docker-maven-plugin in all three of these module's POMs will result in pass-support running mvn verify successfully.

Estimated Severity

Low-Medium. Will it will be successful sometimes, but it is a real problem for Windows developers. This is not an issue for end users.