Found it! One of the guys at the office who is a little more network savvy helped me diagnose the problem step by step. I think this is a form of the 'localhost' vs. address discussions but I didn't understand it's impact here until I saw the network details. A 'netstat' from inside the docker container showed this:
/ # netstat -an Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 127.0.0.1:6300 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN Active UNIX domain sockets (servers and established) Proto RefCnt Flags Type State I-Node Path unix 2 [ ] STREAM CONNECTED 21998 unix 2 [ ] STREAM CONNECTED 22805 where my docker host computer showed this: TCP 0.0.0.0:6300 0.0.0.0:0 LISTENING TCP 0.0.0.0:8080 0.0.0.0:0 LISTENING I thought the local host problem was an outside in issue (tried it on the jacococli command), but I see this was an inside out issue and I needed to set the agent address=0.0.0.0 which solved the problem. Thanks for your responses! -- You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/64f7238e-a13c-443e-b82e-fc91558706c5%40googlegroups.com.
