search

docker / for-win

Bug reports for Docker Desktop for Windows
https://www.docker.com/products/docker#/windows
1.86k stars 292 forks source link

Unable to create...The computer '...' could not be resolved #147

Closed briwilcox closed 6 years ago

briwilcox commented 8 years ago

Expected behavior

Docker daemon with Hyper-V starts at startup

Actual behavior

Docker fails to start

Information

A diagnostic was uploaded with id: EA9197C6-EA7F-4D1B-B97A-9C7C8602B5FF/2016-10-14_14-15-00

Below I've replaced my actual computer name with (computer-name)

[14:07:10.373][Program ][Info ] Version: 1.12.1-stable [14:07:10.457][Program ][Info ] Starting on: 10/14/2016 2:07:10 PM [14:07:10.467][Program ][Info ] Resources: C:\Program Files\Docker\Docker\Resources [14:07:10.477][Program ][Info ] OS: Windows 10 Enterprise [14:07:10.495][Program ][Info ] Edition: Enterprise [14:07:10.509][Program ][Info ] Id: 1607 [14:07:10.521][Program ][Info ] Build: 14393 [14:07:10.548][Program ][Info ] BuildLabName: 14393.321.amd64fre.rs1_release_inmarket.161004-2338 [14:07:10.589][Program ][Info ] Sha1: 995236d98308333f27e3a36505dd761ac9c843f3 [14:07:10.632][Program ][Info ] You can send feedback, including this log file, at https://github.com/docker/for-win/issues [14:07:11.597][TrackingStatus ][Info ] Crash report and usage statistics are enabled [14:07:11.629][Analytics ][Info ] Usage Statistic: appLaunched [14:07:11.745][NamedPipeClient][Info ] Sending Version()... [14:07:11.772][NamedPipeClient][Info ] Received response for Version [14:07:11.779][Analytics ][Info ] Usage Statistic: heartbeat [14:07:11.759][NamedPipeServer][Info ] Version done. [14:07:12.523][NamedPipeClient][Info ] Sending Start(Docker.Core.Settings)... [14:07:12.526][Updater ][Info ] Checking for updates on channel Stable... [14:07:12.534][NamedPipeServer][Info ] Start(Docker.Core.Settings) [14:07:12.545][HyperV ][Info ] Stop [14:07:12.567][PowerShell ][Info ] Run script with parameters: -Stop True... [14:07:12.731][Updater ][Info ] Local build 7135 is as good as the remote 7135 on channel Stable [14:07:17.234][HyperV ][Info ] VM MobyLinuxVM does not exist [14:07:17.258][HyperVGuids ][Info ] Installing GUIDs... [14:07:17.269][HyperVGuids ][Info ] GUIDs installed [14:07:17.280][Firewall ][Info ] Opening ports for C:\Program Files\Docker\Docker\Resources\com.docker.proxy.exe... [14:07:18.435][Firewall ][Info ] Ports are opened [14:07:18.441][HyperV ][Info ] Create [14:07:18.449][PowerShell ][Info ] Run script with parameters: -Create True -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 24 -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso... [14:07:27.545][HyperV ][Info ] Creating Switch: DockerNAT... [14:07:41.909][HyperV ][Info ] Hyper-V is running [14:07:41.909][HyperV ][Info ] Create [14:07:41.909][PowerShell ][Info ] Run script with parameters: -Create True -SwitchSubnetAddress 10.0.75.0 -SwitchSubnetMaskSize 24 -CPUs 2 -Memory 2048 -IsoFile C:\Program Files\Docker\Docker\Resources\mobylinux.iso... [14:07:51.039][HyperV ][Info ] Creating Switch: DockerNAT... [14:08:04.556][NamedPipeServer][Error ] Unable to execute Start: Unable to create: The computer '(computer-name)' could not be resolved. Make sure you typed the machine name correctly and that you have network access. at , : line 340 at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters) at Docker.Backend.ContainerEngine.Linux.Start(Settings settings) at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.b__0(Object[] parameters) at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters) [14:08:04.556][NamedPipeClient][Error ] Unable to send Start: Unable to create: The computer '(computer-name)' could not be resolved. Make sure you typed the machine name correctly and that you have network access. at , : line 340 [14:08:04.571][Notifications ][Error ] Unable to create: The computer '(computer-name)' could not be resolved. Make sure you typed the machine name correctly and that you have network access. at , : line 340 [14:08:11.551][ErrorReportWindow][Info ] Open logs [14:12:20.347][FeedbackSettings][Info ] Open logs

Steps to reproduce the behavior

  1. Boot Windows
joshuaavalon commented 8 years ago

Yes, I am facing the same problem. It works the time when I install it several weeks ago. Today I want to start learning about Docker and I get the same error.

simonferquel commented 8 years ago

Can you upload a diagnostic so we can understand the state of your machine (Settings / Diagnose & Feedback / Upload a diagnostic) ?

dgageot commented 8 years ago

Hi @briwilcox You might want to try the Beta channel instead of the stable one because it contains more recent fixes: https://docs.docker.com/docker-for-windows/

briwilcox commented 8 years ago

@simonferquel A diagnostic was uploaded with id: EA9197C6-EA7F-4D1B-B97A-9C7C8602B5FF/2016-10-14_14-15-00

briwilcox commented 8 years ago

@dgageot I tried docker beta. Fails to start for a similar reason:

Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The computer 'computer name' could not be resolved. Make sure you typed the machine name correctly and that you have network access. at New-Switch, : line 123 at , : line 337 at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters) at Docker.Backend.ContainerEngine.Linux.Start(Settings settings) at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.b__0(Object[] parameters) at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

I've uploaded a separate crash report @ EA9197C6-EA7F-4D1B-B97A-9C7C8602B5FF/2016-10-19_16-00-39 for the beta installation.

casperdcl commented 8 years ago

Similar issue here:

25749FEA-4204-443F-B987-F081E680E169/2016-10-22_13-25-05

My PC was win 8.1, upgraded to 10+hyper V and has zonealarm. I disabled zonealarm completely during installation and startup but docker still fails to start.

briwilcox commented 8 years ago

Just wanted to add this is still happening on Docker v 1.12.3-beta29.2 (8290)

Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The computer (computer name) could not be resolved. Make sure you typed the machine name correctly and that you have network access. at New-Switch, : line 123 at , : line 362 at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters) at Docker.Backend.ContainerEngine.Linux.Start(Settings settings) at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.b__0(Object[] parameters) at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

Crash report here: EA9197C6-EA7F-4D1B-B97A-9C7C8602B5FF/2016-10-27_11-24-57

briwilcox commented 8 years ago

I can stop reporting these if you want but seeing this in the latest beta update: 1.12.3-beta29.3 (8418):

EA9197C6-EA7F-4D1B-B97A-9C7C8602B5FF/2016-11-02_14-26-39

Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The computer '(Computer Name)' could not be resolved. Make sure you typed the machine name correctly and that you have network access. at New-Switch, : line 123 at , : line 362 at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters) at Docker.Backend.ContainerEngine.Linux.Start(Settings settings) at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.b__0(Object[] parameters) at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)

tarunendra commented 8 years ago

Hi, I'm also getting the same issues and below is crash report.

38527887-88C4-47EC-8D21-D98A92197C62/2016-11-08_12-53-42

RootMePLS commented 8 years ago

Temporary fix: write to C:\Windows\System32\drivers\etc\hosts ip address computer name

roolebo commented 7 years ago

@fishhead108 thanks! the workaround works.

daniel-onisoru commented 7 years ago

The workaround with hosts didn't worked for me. I noticed that I have a network adapter called Broken Docker Adapter (20161215T1111536705Z) (1) .. that for some reason exists.

Disabling that did the trick.

Phoenyx33 commented 7 years ago

For me, no broken adapter, hosts didn't work, trying Beta/Experimental didn't work. Added a new Issue with Diagnostic as I found a new glitch to this. It seems to think the mobylinux.iso is invalid and tells me to use a "valid Boot Media". Issue #402 with attached diagnostic number.

wouterds commented 7 years ago

Same issue. Tried uninstalling it, re-installing it, installing the beta version, .. Since the last update of Docker it doesn't start anymore for me. No broken network adapters or anything to see.

(Windows 10 Pro with recent hardware, i5 6600K, Gigabyte Z170N-WIFI, Samsung Pro 840 SSD, ..)

3E50F123-046F-4158-A67E-D4BCD708C35C/2017-01-21_19-25-41

robcthegeek commented 7 years ago

Same issue here - Docker fails to start and it reports that it can't my machine name can't be resolved.

:boom: Crash Report: 93F4B946-F34A-4EBF-AFC6-B3F6151F3464/2017-01-23_09-26-59

Tried a complete re-install, no dice.

Let me know if there's anything you want me to try/guinea pig. I need to get this up and running ASAP! 😄

Update

The HOSTS file fix (adding the machine name with loopback address) worked! 😁 🎉

casperdcl commented 7 years ago

Personally there was no way for me to get around this other than leaving ZoneAlarm permanently uninstalled. If anyone has zonealarm + docker + win10 all working harmoniously do let me know.

zezke commented 7 years ago

I ran into the same issue after installing the latest update. However @fishhead108's suggestion to edit the hosts files fixed my issue.

djmarland commented 7 years ago

I also encountered the same problem after updating to 1.13. To find my loopback address I typed Ping Loopback into Powershell. It turns out my loopback address is in IPv6, so that was what I added to the hosts file (as my original attempt of 127.0.0.1 wasn't working).

::1 COMPUTERNAME

Seems to be working now

rn commented 7 years ago

I've changed the title to better reflect the issue.

On our systems we do not have the computer name in C:\Windows\System32\drivers\etc\hosts and don't encounter the issue so I'm a little at a loss here why this fails for some users. However, the workaround seems easy and straight forward.

nsgundy commented 7 years ago

Ran into the same issue today. Had a different issue first after updating to the latest version 17.03.0-ce-win1 (10296) and followed a recommendation to reset the network adapters on Windows 10 via Settings > Network&Internet > Status > Network Reset. After rebooting and trying to start Docker again, I am presented with the issue here: Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The computer 'COMPUTERNAM' could not be resolved. Make sure you typed the machine name correctly and that you have network access.

The strange thing is that COMPUTERNAM in my case is missing a character at the end and therefore it makes sense that it doesn't resolve. The length of the computer-name in my case is 16, but docker is reporting on 15.

Edit If I go to the TCP/IP settings of my network interface Advanced > WINS and Disable NetBIOS over TCP/IP, the issue disappears (meaning the error message isn't the one mentioned here).

Edit2 Seems like what I last posted isn't correct. Tried to reset my docker install and am now back to the same issue, even with NetBIOS is disabled.

dnunes commented 7 years ago

I just ran into the same issue.

For me, simply disabling the vmWare Network Adapters (I had two) did the trick. Docker may have used the wrong one while trying to run or something?

vitr commented 7 years ago

I just had the same error, in my case, the solution was about renaming my computer image See my 'Full Computer Name' was a way longer than 16 chars and docker shorted it to just 16 chars. After renaming my computer to a shorter name the issue has gone.

nsgundy commented 7 years ago

A fix would be appreciated... I for one have no ability to change my computer name (domain workstation).

Phoenyx33 commented 7 years ago

I haven't had a chance to check this, but I noticed I had 4 docker adapters and 2 switches (actually hyperv items) when I turned on a device manager switch to view "dead devices". I need to try reinstalling Docker for Windows now that I have deleted those, but I'm with a friend at the hospital atm and it may take me awhile to get to that.

Sent from my Sprint Samsung Galaxy S® 6.

-------- Original message -------- From: Gundy notifications@github.com Date: 3/24/17 9:00 AM (GMT-05:00) To: docker/for-win for-win@noreply.github.com Cc: "K. Benson" phoenyx33@outlook.com, Comment comment@noreply.github.com Subject: Re: [docker/for-win] Unable to create...The computer '...' could not be resolved (#147)

A fix would be appreciated... I for one have no ability to change my computer name (domain workstation).

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/docker/for-win/issues/147#issuecomment-289016242, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATTDApWledzbovWoZSrDqgAO_3qC82q8ks5ro75ggaJpZM4KXc0l.

jasonbivins commented 7 years ago

@briwilcox

Do you any additional virtual switches in your Hyper-V or do you only have the DockerNat ?

Phoenyx33 commented 7 years ago

Just the dockernat for me.

Sent from my Sprint Samsung Galaxy S® 6.

-------- Original message -------- From: Jason Bivins notifications@github.com Date: 6/7/17 12:48 PM (GMT-05:00) To: docker/for-win for-win@noreply.github.com Cc: "K. Benson" phoenyx33@outlook.com, Comment comment@noreply.github.com Subject: Re: [docker/for-win] Unable to create...The computer '...' could not be resolved (#147)

@briwilcoxhttps://github.com/briwilcox

Do you any additional virtual switches in your Hyper-V or do yo only have the DockerNat ?

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/docker/for-win/issues/147#issuecomment-306855423, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATTDAiXS_QvLX4He4XhBDPOOOotYhM2Fks5sBtRRgaJpZM4KXc0l.

adambertalan commented 7 years ago

@vitr The computer renaming method did the trick for me! Thanks!

llaslo commented 7 years ago

I had the same problem running on a Windows 10 Pro VM in VMWare Fusion Pro 8. The issue was that it was truncating the computer name. My computer name was: IT100012-Win10VM but Docker was giving an error resolving IT100012-Win10V. I worked around this by adding the following line to my host file: ::1 localhost IT100012-Win10V

jasonbivins commented 6 years ago

closing - pinata issue was closed and I can no longer repro this as of 17.09 CE

LenaWil commented 6 years ago

@jasonbivins I have the same problem, should I open a new issue?

ddwagner commented 5 years ago

This is still happening to me as well. Updated to latest docker desktop (2.0.03) today and all of a sudden it couldn't resolve the computer name. Fixed by shortening the name. New issue time?

robert-mccarter commented 5 years ago

Like @vitr renaming my computer worked for me (although I completely get that not everybody can do that). I had a very long name and Docker was cutting off the name, so my guess is the truncated name didn't work.

LenaWil commented 5 years ago

Because of university policy, I'm not allowed to rename my computer. Is there another workaround?

robert-mccarter commented 5 years ago

I'm not sure @TijmenW, the only thing I can think of is that you could grab the truncated name Docker is trying to use, and then add that into your hosts file mapping it to the full name, or localhost. No idea if that will work though.

ChristopherBull commented 5 years ago

Just to echo others here, I had this problem today. Renaming my computer to 15 chars or less worked for me. Would be good to have this automatically detected and fixed, rather than requiring people to edit a hosts file.

LenaWil commented 5 years ago

@CaffeinatedAndroid It bothered me too, so I opened a issue. #4192

JonnyD07 commented 5 years ago

I had this same issue. I had VirtualBox installed on my PC, which I believe was starting up at the same time as Docker. Uninstalling VirtualBox fixed the issue for me.

docker-robott commented 4 years ago

Closed issues are locked after 30 days of inactivity. This helps our team focus on active issues.

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. /lifecycle locked