Firewall exceptions worked once, but not subsequently












0














Been trying for a few weeks to get this issue resolved:



Docker "waiting for an IP" when starting or creating new machine



Basically, docker-machine times out waiting for an IP.



I got it working once yesterday. I made firewall exceptions for docker-machine.exe, VirtualBox.exe, VirtualBoxVM.exe, VBoxHeadless.exe, and VBoxManage.exe. Finally, it was able to acquire an IP address and, for a few minutes, I was able to connect docker in WSL to the Windows docker-host.



Then tried to docker-machine restart docker-host to make sure it was persistent and it was unable to acquire an IP address. Have tried several dozen attempts to rm and create the docker-host and the problem persists.



Verified the firewall exceptions are still there, restarted, verified, etc.



So, is there something that could be causing this behavior? Not working for dozens of attempts, working once, then not working again for another dozen.



The setup I'm trying to implement works fine at home, but work computer not so much. This is the implementation: https://www.paraesthesia.com/archive/2018/09/20/docker-on-wsl-with-virtualbox-and-docker-machine/










share|improve this question






















  • Are you sure that you are reliably able to get dhcp service? Are you sure you have a firewall problem and not another network problem all together?
    – Andy
    2 days ago
















0














Been trying for a few weeks to get this issue resolved:



Docker "waiting for an IP" when starting or creating new machine



Basically, docker-machine times out waiting for an IP.



I got it working once yesterday. I made firewall exceptions for docker-machine.exe, VirtualBox.exe, VirtualBoxVM.exe, VBoxHeadless.exe, and VBoxManage.exe. Finally, it was able to acquire an IP address and, for a few minutes, I was able to connect docker in WSL to the Windows docker-host.



Then tried to docker-machine restart docker-host to make sure it was persistent and it was unable to acquire an IP address. Have tried several dozen attempts to rm and create the docker-host and the problem persists.



Verified the firewall exceptions are still there, restarted, verified, etc.



So, is there something that could be causing this behavior? Not working for dozens of attempts, working once, then not working again for another dozen.



The setup I'm trying to implement works fine at home, but work computer not so much. This is the implementation: https://www.paraesthesia.com/archive/2018/09/20/docker-on-wsl-with-virtualbox-and-docker-machine/










share|improve this question






















  • Are you sure that you are reliably able to get dhcp service? Are you sure you have a firewall problem and not another network problem all together?
    – Andy
    2 days ago














0












0








0







Been trying for a few weeks to get this issue resolved:



Docker "waiting for an IP" when starting or creating new machine



Basically, docker-machine times out waiting for an IP.



I got it working once yesterday. I made firewall exceptions for docker-machine.exe, VirtualBox.exe, VirtualBoxVM.exe, VBoxHeadless.exe, and VBoxManage.exe. Finally, it was able to acquire an IP address and, for a few minutes, I was able to connect docker in WSL to the Windows docker-host.



Then tried to docker-machine restart docker-host to make sure it was persistent and it was unable to acquire an IP address. Have tried several dozen attempts to rm and create the docker-host and the problem persists.



Verified the firewall exceptions are still there, restarted, verified, etc.



So, is there something that could be causing this behavior? Not working for dozens of attempts, working once, then not working again for another dozen.



The setup I'm trying to implement works fine at home, but work computer not so much. This is the implementation: https://www.paraesthesia.com/archive/2018/09/20/docker-on-wsl-with-virtualbox-and-docker-machine/










share|improve this question













Been trying for a few weeks to get this issue resolved:



Docker "waiting for an IP" when starting or creating new machine



Basically, docker-machine times out waiting for an IP.



I got it working once yesterday. I made firewall exceptions for docker-machine.exe, VirtualBox.exe, VirtualBoxVM.exe, VBoxHeadless.exe, and VBoxManage.exe. Finally, it was able to acquire an IP address and, for a few minutes, I was able to connect docker in WSL to the Windows docker-host.



Then tried to docker-machine restart docker-host to make sure it was persistent and it was unable to acquire an IP address. Have tried several dozen attempts to rm and create the docker-host and the problem persists.



Verified the firewall exceptions are still there, restarted, verified, etc.



So, is there something that could be causing this behavior? Not working for dozens of attempts, working once, then not working again for another dozen.



The setup I'm trying to implement works fine at home, but work computer not so much. This is the implementation: https://www.paraesthesia.com/archive/2018/09/20/docker-on-wsl-with-virtualbox-and-docker-machine/







networking windows-10 firewall






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 2 days ago









sockpuppetsockpuppet

1154




1154












  • Are you sure that you are reliably able to get dhcp service? Are you sure you have a firewall problem and not another network problem all together?
    – Andy
    2 days ago


















  • Are you sure that you are reliably able to get dhcp service? Are you sure you have a firewall problem and not another network problem all together?
    – Andy
    2 days ago
















Are you sure that you are reliably able to get dhcp service? Are you sure you have a firewall problem and not another network problem all together?
– Andy
2 days ago




Are you sure that you are reliably able to get dhcp service? Are you sure you have a firewall problem and not another network problem all together?
– Andy
2 days ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390747%2ffirewall-exceptions-worked-once-but-not-subsequently%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390747%2ffirewall-exceptions-worked-once-but-not-subsequently%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to make a Squid Proxy server?

Is this a new Fibonacci Identity?

19世紀