Private network issues with docker

I’m having trouble connecting to MongoDB on the docker host. I’m not sure what the problem is but my current docker container should be able to connect with a non-docker MongoDB instance.

My host has 2 network interfaces which are eth0 with an outbound IP and eth1 with a private lan ip 192.168.100.200. Is there any way to connect to the host without doing –net=host?

  • docker-machine stop command kills all my containers
  • ecs-cli compose service up doesn't terminate
  • How can I add hostnames to a container on the same docker network?
  • Spring docker volume and autoreload
  • Where does the convention of using /healthz for application health checks come from?
  • How to kill used port of docker
  • Provide environment variables to elastic beanstalk docker deployment
  • How can I tell if docker daemon fails?
  • Failed to limit memory with docker compose
  • Why does running some docker images must add a command?
  • replicas of a service in docker swarm remain 0/1 forever
  • how to clean up docker overlay directory?
  • One Solution collect form web for “Private network issues with docker”

    Can you enter in your MongoDB using nsenter or docker exec, and issue some commands such as

    ip all
    

    using

    nsenter
    

    from https://github.com/jpetazzo/nsenter
    or

    docker exec
    

    if you have a recent version of docker

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.