Question

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

Hi,

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?

Thanks.

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

sandymcp • December 6, 2018
eval $(docker-machine env test123)
export DOCKER_HOST=$(doctl compute droplet ls --format PrivateIPv4 --no-header test123
Jamison Greeley • November 2, 2018

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?

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up