Not able to connect docker from host when network change

[kusumat]

Hi ,

I am not able to connect to docker container when there is network/ip change from office to home. But the same works with localhost or 127.0.0.1

I am connecting to VPN to connect to database.

Thanks,
Kusuma

[kusumat]

root@1c970ed5cd64:/etc# curl http://localhost:8090/admin/health_check/all
{"health":"passed"}root@1c970ed5cd64:/etc# curl http://172.17.0.2:8090/admin/health_check/all
{"health":"passed"}root@1c970ed5cd64:/etc# curl http://192.168.0.103:8090/mfconsole/health_check/all
curl: (7) Failed to connect to 192.168.0.103 port 8090: Connection refused

[kusumat]

When i update docker run like
docker run --net=10.10.33.33 --name $CONTAINER_NAME -d -p $INPUT_PORT:$INPUT_PORT -p $DEBUG_PORT:$DEBUG_PORT $IMAGE_NAME

C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: network 10.10.33.33 not found.
ERROR: Docker failed to run the mycontainer container !

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked