How to force docker-machine to use private IP instead public


I’m using GitLab runners in autoscale mode with DigitalOcean. I notice that GitLab runner by using Docker Machine use Public IP instead Private. I precise --digitalocean-private-networking option, but it changes nothing.

When I docker-machine inspect my-machine I saw "PrivateNetworking": true but "IPAddress" is a public one.

Does this the normal behavior? Does this could be changed?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

eval $(docker-machine env test123)
export DOCKER_HOST=$(doctl compute droplet ls --format PrivateIPv4 --no-header test123

I’d like to know this too. Currently, I’m having to allow all 2376/tcp traffic from anywhere in the world through my firewall, and I’d really rather not. Can I force docker-machine to use the internal IP?