I had 3 droplets running with a private network setup. Recently I had to destroy and recreate one of the droplets. The new droplet cannot longer talk on the private network. Its eth1 interface seems completely shut off from the rest of the world.
To recreate the droplet I used the same command I had previously used:
docker-machine create --driver digitalocean --digitalocean-access-token $DIGITAL_OCEAN_TOKEN \ --digitalocean-image ubuntu-18-04-x64 --digitalocean-size s-4vcpu-8gb --digitalocean-region nyc3 \ --digitalocean-private-networking --digitalocean-monitoring \ --digitalocean-ssh-key-fingerprint MY_FINGERPRINT MY_HOST
I specifically checked the file
/etc/netplan/50-cloud-init.yaml and it looked correct and I could see
eth1 listed in there.
Any steps you can provide me on debugging this issue?
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.
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.
Click below to sign up and get $100 of credit to try our products over 60 days!