-
Notifications
You must be signed in to change notification settings - Fork 287
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
Lab - Multi-Container Applicationns - not going through #196
Comments
@eliassal can you check whether you have network access from within containers? Eg. try running |
no, this is the output |
Pining @kallie-b and @JMesser81 - are there generalized networking troubleshooting steps on Windows 10? |
I believe we do have some--double checking with the team on the best steps for this, and will return with an answer as soon as possible. |
@eliassal -- I apologize for the delayed reply. Could you please run the following commands and share the results? They should help us get the details on your connectivity issue. From your container host:
From inside the container: |
Hi, here is the outcome fo Name SwitchType NetAdapterInterfaceDescription External External Realtek USB GbE Family Controller Get-netnat Get-netnatstaticmapping : Gives nothing Ipconfig /allcompartments /allNetwork Information for Compartment 1 (ACTIVE)Host Name . . . . . . . . . . . . : sierac Ethernet adapter vEthernet (Internal Ethernet Port Windows Phone Emu Connection-specific DNS Suffix . : Ethernet adapter vEthernet (HNS Internal NIC): Connection-specific DNS Suffix . : Tunnel adapter Local Area Connection: Connection-specific DNS Suffix . : Ethernet adapter vEthernet (External): Connection-specific DNS Suffix . : Wireless LAN adapter Local Area Connection* 2: Media State . . . . . . . . . . . : Media disconnected Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Wireless LAN adapter Wi-Fi: Media State . . . . . . . . . . . : Media disconnected Tunnel adapter isatap.{E02DE864-01BC-4A8F-92BB-D886C127F16B}: Media State . . . . . . . . . . . : Media disconnected Tunnel adapter isatap.{9E78FE32-D979-401B-A592-B7F858221B86}: Media State . . . . . . . . . . . : Media disconnected Tunnel adapter isatap.{FFECA9A8-0CDF-447C-B32C-F7133FA7A4D1}: Media State . . . . . . . . . . . : Media disconnected Tunnel adapter isatap.{8DEB2D62-D552-41AD-A06C-40D48C6D6D3E}: Media State . . . . . . . . . . . : Media disconnected |
So we need to explore what's going on with your switches, to make sure your container has proper access to the nat network to get external connectivity. First, run these from the container host:
Next, run any container (for example, you could run a NanoServer image in interactive mode with |
Get-ContainerNetwork Name Id Subnets Mode SourceMac DNSServers DNSSuffix nat ff909283-0245-4a82-a407-a37fbc872fbb {172.31.0.0/20} NAT Get-NetNatExternalAddress ExternalAddressID : 0 ExternalAddressID : 1 ExternalAddressID : 2 ExternalAddressID : 3 ExternalAddressID : 1000000 ExternalAddressID : 1000001 ExternalAddressID : 1000002 ExternalAddressID : 1000007 ExternalAddressID : 1000008 ExternalAddressID : 1000009 ExternalAddressID : 1000010 ExternalAddressID : 1000011 ExternalAddressID : 1000012 Then I ran Windows IP Configuration Host Name . . . . . . . . . . . . : 89514939f2b7 |
Apologies for the delay, and for the inconvenience of this error. Next we'd like to get your HNS and Docker Daemon logs, and they should give us a better idea of what's happening. Please run each of the following commands on your host machine:
Now reproduce the actions you've taken to get the connection error (so, 'docker-compose ... build,' I believe). Now stop the event session: Once you've completed these steps please provide:
|
1st of all, dockerd is not in C:\Windows\System32 I followed all steps (HNS.etl included herewith), but I have no log file where Dockerd is found. Now when I ran `I am getting a very strange error as follows
|
I dont the HNS file attached, I tired several times but it is not getting attached |
@eliassal--could you email me at kallie.bracken@outlook.com? That might be an easier way for you to share the logs. Also, the Docker daemon log will not be saved as a file--we're looking for the output of the command, Also, ensure that you're stopping the docker service before running any of the above commands (Stop-Service docker). |
I shared the file by email. |
No, as long as you're running the command from an elevated session ("Run as Administrator"), there shouldn't be any difference running between one or two sessions. I received your file--let me check with my team and see where we should go next. |
sorry, please ignore the 1st file I sent, I have sent 2 new files dockerd full output, new hns.etl, both have now muche more data. Also, I provided a snapshot of the error and the dockerd output |
Can you try/report the following:
Now reproduce the steps you took to get the error (run docker-compose...)
|
Hi, here is a ping to from host dotnet.myget.org
2nd, dotnet.myget.org is in the NuGet.config, I replaced
|
when I run I get
|
Alright, so the ping to dotnet.myget.org may be being blocked for some reason, so it may not be a good test. Try this: (The JSON file you're downloading will be saved as test.out) That works on my system, and if that works for you we'll know that the issue isn't related to your host having problems with external connectivity. |
Hi Kali, any feedback on this ? Regards, Salam From: Kallie [mailto:notifications@github.com] So we need to explore what's going on with your switches, to make sure your container has proper access to the nat network to get external connectivity. First, run these from the container host: Get-ContainerNetwork Next, run any container (for example, you could run a NanoServer image in interactive mode with docker run -it nanoserver cmd) and from inside the container, run: — |
Hi--Were you able to do this?
|
Yes I was able to do and even sent you the the test.out by email. However, I have some good news, after installing the updates KB3200970 (as indicated oiin the thread I opened for win2k16 box at https://social.msdn.microsoft.com/Forums/en-US/e1962669-2359-4343-a179-8e434be8356d/docker-is-not-able-to-pull-images-on-win2k16?forum=windowscontainers). Thanks for your help |
Sorry Kali, I responded very quickly, it is still not working and giving the same exact error. The command
was already working fine |
Hi Kali, any feedback so far? |
Hi--apologies for the delay. I don't have feedback yet, but I'll get it to you as soon as possible. |
Salam--I've sent you an email regarding the next step we should take to sort this out. |
It seems that the problem here was that the "bridge=none" option was enabled in eliassal's docker deamon file. This was preventing container endpoints from gaining external connectivity because they were not being connected to the default nat network that is automatically created by Docker and Windows. The lab that eliassal is using here follows similar steps to those described in this blog post, which was recently published by my team. The post explains some of the details behind the basics of compose and container networking on Windows, so it may be helpful to anyone running into issues in this area. |
@kallie-b thanks for helping to debug this. Can this issue be closed? |
Yes it can, thank you :) |
So many thanks for the team who spent more than hour debugging and unearth the root cause of the issues, special thanks to Kali and Vikrant. I wish all support team for other software can provide such freindly support. IN fact I used a daemon.json file with parameteres that were not needed and one of them which caused the network issue was "bridge=none" which is specific to linux machines |
Okay, so you don't have external connectivity from your containers? Do you mind copying and pasting the contents of your daemon.json file? Also, will you do the following and report the results back to me?
This info should help me assist you with troubleshooting! |
Hi Kali, I presume that this response is for mfaizance. I still have the issue #27911 with docker on win2k16 box where I can not run a basic command.box Vikrant tried to help when we were in the skype session. I did not see any response from Patrick since you responded following our session. |
Right, yes it is--thank you. I forgot to @ mention him. I'll take a look at your other issue and see if I can get someone's attention about it. Happy Holidays! |
Thank you @kallie-b for your response. I have shared the details below: My environment: Docker version: Server: Docker daemon.json Get-ContainerNetwork
Get-NetNatExternalAddress
I have run two containers using docker run -it microsoft/nanoserver powershell If I run a container docker run -it microsoft/nanoserver powershell
But if I ping www.google.com ipconfig /all from insode the container
|
We need to see if you have DNS configured on your host--it looks like you don't have external DNS configured on the containers. Please run the following from your host and report back the results:
|
Hi Kallie,
Here is the output, I have a DNS which is the same for all my
Windows IP Configuration
Host Name . . . . . . . . . . . . : myServer
Primary Dns Suffix . . . . . . . : my.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : my.net
Ethernet adapter vEthernet (HNS Internal NIC):
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
Physical Address. . . . . . . . . : 00-15-5D-F8-EB-F1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::18ee:4860:e154:39b%2(Preferred)
IPv4 Address. . . . . . . . . . . : 172.18.240.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.240.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 184554845
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-51-DD-78-00-15-5D-01-16-06
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter #2
Physical Address. . . . . . . . . : 00-15-5D-01-16-29
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::55f8:f821:902f:312f%4(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.34(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, December 22, 2016 8:22:53 PM
Lease Expires . . . . . . . . . . : Saturday, December 31, 2016 8:22:53 PM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 218109277
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-51-DD-78-00-15-5D-01-16-06
DNS Servers . . . . . . . . . . . : 192.168.1.13
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{2AEC5B1B-C9CD-45A5-B7CA-2CA1416BCAB6}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{105D1228-2853-4526-9C6B-B431367BF892}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
From: Kallie [mailto:notifications@github.com]
Sent: jeudi 29 décembre 2016 20:53
To: docker/for-win <for-win@noreply.github.com>
Cc: eliassal <salamadmin@free.fr>; Mention <mention@noreply.github.com>
Subject: Re: [docker/for-win] Lab - Multi-Container Applicationns - not going through (#196)
We need to see if you have DNS configured on your host--it looks like you don't have external DNS configured on the containers. Please run the following from your host and report back the results:
get ipconfig /all
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#196 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AIDneKdmvCfZzFu54Imv6cazyN8RApvVks5rNA-pgaJpZM4Knmx8> . <https://github.com/notifications/beacon/AIDneOJ2JocNb032CY6YhSOlgrZysbqvks5rNA-pgaJpZM4Knmx8.gif>
|
Sorry, was this for me or for mfaizanse? I responded quickly as I thought you were chasing the issue of not being able to pull on the other machine with win2K16 |
Apologies, this was for mfaizanse. I will remember to mention him from now on to avoid ambiguity! |
Thanks @kallie-b for your time. I somehow got the issue resolved. I don't know the exact solution but I hit and tried some settings of default nat adapter and then reinstalling the docker resolved the issue..:) |
Good to hear, I'm glad you got it resolved. If you figure out exactly what was going wrong do let me know :) |
Hoping someone else might benefit from my lesson learned: I was seeing the same "WaitNamedPipe" error while trying to run through the Eventuate.io demo after having just installed native Docker for Windows on Windows 10 Pro 64-bit. The problem was solved by a restart. I was setting up a new laptop and had completed numerous installs. I guess after all the restarts, I hadn't noticed that the Docker installer didn't force me to do a restart. Once restarted, the normal Docker startup messages appeared and everything worked as expected.
Best of luck. |
@rlyders Thanks for the tip. I'm also on Windows 10 Pro 64-bit and a restart worked for me. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
I am trying to follow the lab at
https://github.com/docker/labs/blob/master/windows/windows-containers/MultiContainerApp.md
I have a physical win laptop with windows container enabled as well as HyperV
Whenever I issue the command
docker-compose -f .\docker-compose.windows.yml build
docker get stuck on step 8/13 and sends back
Thanks for your help
The text was updated successfully, but these errors were encountered: