use docker container on host network without sharing host's ip

My docker host is part of the local network 192.168.178.0/24.

Is there a way to run a container that becomes a part of the host network, but does not share the same ip as the host? So for example if the host has the ip 192.168.178.5 i’d like to provide 192.168.178.8 to the container without interfering with the docker host’s network configuration.

  • docker-compose Rails spring doesn't work
  • Does all running docker containers have a separate process ID
  • Tunnel Connection Failed error when logging into artifactory docker registry
  • Docker container access to swarm IPs
  • Docker inspect format to retreive IP of a particular network
  • pg_dump in docker: “could not open output file” “protocol error”
  • Can't use 127.0.0.1 to connect mysql server docker container, but can use IP?
  • docker base image: how to upgrade
  • Saving changes in docker project
  • docker-compose error on the Django's welcome page
  • Setting $PATH in docker image?
  • docker elasticsearch container not forwarding port
  • One Solution collect form web for “use docker container on host network without sharing host's ip”

    since a docker container is by nature bound to use the networking stack of it’s host, it also has to share the hosts IP to communicate with the network. For a one-container setup, the only solution should be to add a second NIC to the host and use that second NIC and the provided IP exclusively for your docker… But apart from that I don’t see any solution that does not deeply mutilate the OSI model of your host’s network stack and thus include some major side-effects :-/

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