Running containers inside custom network provide you ability to sign containers with names, and use these names as DNS, avoiding IP utilization, like - docker network create mysupernetwork, docker run -d MyImageName (any other options) --name backend --network mysupernetwork and get access to it via http://backend from any other containers inside this network instead of http://127.17.0.1:8080 or whatever.
If you really need to have a stable IP you have to run containers in the same order each time. For example it could be done with the docker-compose.yml where you will make a Chain for all containers using depends_on option.