-
Notifications
You must be signed in to change notification settings - Fork 36
dockerComposeRestart and the network limit #39
Comments
Hi @mb720, I'm glad that you are enjoying the Plugin! There is code in the plugin to remove any networks that are created. However, it needs to know the name of the docker machine being used if it's something other than There is a
Here is the plugin code for network removal that should run when the containers are stopped during the restart process:
Hopefully that is the issue. Otherwise, we will have to investigate further. |
Thanks for your quick reply, Kurt! Ah, I see. I was wondering why I was getting those errors every time I called
After adding the following to Is that the I should mention that I'm currently on Windows 10 x64. |
Hi @mb720, Happy to hear that it's working for you now! And it's really great to hear you are on Windows 10 as the code was written to not have anything that was OS dependent but we never tested it before on Windows 10. Yes, Thanks again for using the plugin and providing feedback! |
Hi!
Having a great time with your plugin!
When developing, I use
dockerComposeRestart
to restart my application with the changes I made to it.This works great for a while, but since there's a limitation to the number of Docker networks you can have, I get this message when trying to create the 32nd network :
After removing a network, I can start the application again.
I guess this could be fixed if
dockerComposeRestart
were an alias fordocker-compose down && docker-compose up
sincedocker-compose down
removes the network.Thanks!
The text was updated successfully, but these errors were encountered: