-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docker network support for docker provider #6667
Comments
Very good point!
and then use an ugly hack to run the container in the foo network, for example:
So, would nice to have this implemented in a more friendly way with "vm.network " configuraion instead of manual steps to create/destroy the net |
Use Docker Compose? :) |
Aye. Been working on some scripts to set up docker-machine and docker-compose to emulate the provisioning we currently do in Vagrant. |
But emulating is only a w/a, I have one for my case as well. But that is not a fix. |
You can use Docker Compose with Vagrant (that's what I do). Someone even made a plugin to simplify things :) https://github.com/leighmcculloch/vagrant-docker-compose |
@teohhanhui it is the provisioner. It cannot configure networks for the docker provider |
Uhh I gave up pretty quickly the first time I tried the Docker provider (I need a consistent cross-platform solution anyway, so a good-old VM it is) |
Closing via #8576 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Is there an ETA for
docker network
support for the Docker provider?https://docs.docker.com/engine/userguide/networking/dockernetworks/
The text was updated successfully, but these errors were encountered: