Docker build on different machine/network than image deploy

our parent organization built a docker image on a network not available to our organization. As a result, we cannot start-up all aspects of the container. Certain IP addresses in the build-process are somehow integrated into the image. Additionally, the docker image, when “run”, isn’t creating the eth0 interface and assigning an IP address. any ideas that jump right out?

I understand that docker is “supposed” to rewrite /etc/hosts, /etc/hostnames, and /etc/resolv.conf