Podman in VM -

[cliffwoodger]

Hi All,
We have Podman running within WSL on a Windows VM.
The container app hosted by Podman needs to access a SQLServer DB on the same VM.
When the VM restarts, its IP address changes.
We have read that the way to avoid the DB connectivity issue is to use host.docker.internal
However, this isn't working for us and, when we use netcat, we get the following error:

nc host.docker.internal 1433 -v

nc: connect to host.docker.internal (169.254.1.2) port 1433 (tcp) failed: Connection refused
Looks like it can see the target but that there is a permissions/privileges issue.
Can anyone help with this... provide any suggestions on how to get round this etc.
Many thanks,
Cliff

[baude]

there is lots of missing details here so it makes it hard to address directly what you should do. For example, running privileged or not. Would running the SQL service with host networking be something you could consider?

if this were me, however, i would likely consider running the two in a pod because they share the same network namespace making networking basically a no-op. You could also run in a pod using a domain socket that both containers in the pod can see?

i hope the hints help.