Joerg Kastning

@richm - Reproduced as broken with containers.podman 1.12.0 - Confirm as fixed with containers.podman 1.14.0

Dear all, I'm facing this issue as well. The following screenshot shows that I'm using the IP address to check the service.  The monitor is configured to accept the...

Hi, here is the network setting for the running container: ``` "NetworkMode": "pasta", "PortBindings": { "3001/tcp": [ { "HostIp": "0.0.0.0", "HostPort": "3001" } ] }, --- networkBackend: netavark networkBackendInfo: backend:...

Here is the information you requested: ``` $ ss -tuln | grep 8000 tcp LISTEN 0 4096 *:8000 *:* $ sudo firewall-cmd --list-ports 8000/tcp ``` I did some further testing...

> So the issue is with the network or namespace configuration of my podman environment. I will work on the issue and post the solution here as well as soon...

I cannot check anymore as I did stop using VSCodium.

OK, then let me edit the PR to put the example in the code of the module. -- E-Mail: ***@***.*** Twitter: https://twitter.com/JoergKastning Internet: https://www.my-it-brain.de Threema-ID: K2Y6W49N OpenPGP-ID: 7A302E30 OpenPGP-Fingerabdruck: 2026...

Hi @mariolenz , I moved the example from the .rst file to the module code. Could you please check if it's OK now? Cheers, Tronde

Sorry, I may need some help here as I cannot figure out what I did wrong causing the ansible/check to fail.

> > Sorry, I may need some help here as I cannot figure out what I did wrong causing the ansible/check to fail. > > I don't understand why this...