Ann - sorry to say that does not help me very much.
Another bit of information …
The issue occurs in a jenkins job, which implements a repeatable process to create and provision dockers for the nginx proxy, sq, and postgres. The job works just fine and has done for several months. The containers run and I can successfully process scans from sonar-scanner against them from other jenkins build pipelines.
The reported issues occur in a newly added build step to run an automated test of the build-started images.
I had thought that the issue occurred because the test was being run before the server had initialized. I believe I have ruled this out by putting a wait in the pipeline and hitting the server URL with curl (to simulate a browser interaction) before running the test. However that does not seem to have done the trick.
I also notice that there is another post in this forum that looks suspiciously similar that report the same issue occurring from jenkins. Issue regarding sonarqube jenkins integration
No clear resolution in the post …
I suppose the next step is to try kicking off the test in a subsequent build and see if that will run the test - not an elegant solution. I’d prefer a real fix.