Report this

What is the reason for this report?

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

Posted on August 3, 2018

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.



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!

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.

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?

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

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.