Docker Community Forums

Share and learn in the Docker community.

Error When Running Hello-World: Failed to attach network endpoint to Container


I’m new to docker.

I have followed the steps for the installation of docker on Windows Server 2016 according to the documentation , and getting responses for docker info and docker version commands. I have successfully loaded hello-world images from another computer, because there is limited access for the server. When docker images command run, it shows hello-world image in the list. But, when I run docker run hello-world command I get the error behind Actual Behavior.

Expected behavior

Hello-World verification is expected to run, as stated in the documentation.

Actual behavior

Giving the error for run hello-world command:
PS> docker run hello-world
C:\Program Files\docker\docker.exe: Error response from daemon: CreateComputeSystem fb69c3ce1994464e62ee7f01213fe5b59177
1ef4151af88686e17500facc4ba0: The parameter is incorrect.
[Event Detail: Failed to attach network endpoint to Container ‘fb69c3ce1994464e62ee7f01213fe5b591771ef4151af88686e17500f
acc4ba0’, network endpoint ID ‘{########-####-####-####-############}’: One or more arguments are invalid (0x80070057).
Provider: 17103e3f-3c6e-4677-bb17-3b267eb5be57 EventID: 12102]
(extra info: {“SystemType”:“Container”,“Name”:“fb69c3ce1994464e62ee7f01213fe5b591771ef4151af88686e17500facc4ba0”,“Owner”


Symantec AV is installed but disabled and stopped. Windows Firewall is stopped. FireEye Endpoint Agent is working and cannot be stopped.

PS> docker version
Client: Docker Engine - Enterprise
Version: 18.09.5
API version: 1.39
Go version: go1.10.8
Git commit: be4553c277
Built: 04/11/2019 06:44:52
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine - Enterprise
Version: 18.09.5
API version: 1.39 (minimum version 1.24)
Go version: go1.10.8
Git commit: be4553c277
Built: 04/11/2019 06:43:04
OS/Arch: windows/amd64
Experimental: false

PS> docker info
Containers: 10
Running: 0
Paused: 0
Stopped: 10
Images: 27
Server Version: 18.09.5
Storage Driver: windowsfilter
Logging Driver: json-file
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
Log: awslogs etwlogs fluentd gelf json-file local logentries splunk syslog
Swarm: inactive
Default Isolation: process
Kernel Version: 10.0 14393 (14393.2906.amd64fre.rs1_release_inmarket.190401-1809)
Operating System: Windows Server 2016 Standard Version 1607 (OS Build 14393.2906)
OSType: windows
Architecture: x86_64
CPUs: 8
Total Memory: 64GiB
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Experimental: false
Insecure Registries:
Live Restore Enabled: false
-the output of:
- Debug-ContainerHost.ps1 using Powershell on Windows:

Describing Windows Version and Prerequisites
[+] Is Windows 10 Anniversary Update or Windows Server 2016 1.18s
[+] Has KB3192366, KB3194496, or later installed if running Windows build 14393 225ms
[+] Is not a build with blocking issues 58ms
[+] Has ‘Containers’ feature installed 17.58s
Describing Docker is installed
[+] A Docker service is installed - ‘Docker’ or ‘com.Docker.Service’ 286ms
[+] Service is running 79ms
[+] Docker.exe is in path 2.19s
[+] Docker is registered in the EventLog service 88ms
Describing User has permissions to use Docker daemon
[+] docker.exe should not return access denied 221ms
Describing Windows container settings are correct
[+] Do not have DisableVSmbOplock set to 1 89ms
[+] Do not have zz values set 91ms
[+] Do not have FDVDenyWriteAccess set to 1 88ms
Describing The right container base images are installed
WARNING: No* base images found. Checking for deprecated images.
At least one of '', '', '' or deprecated microsoft/windowsservercore, microsof
t/nanoserver should be installed 553ms
ValidationMetadataException: The argument is null or empty. Provide an argument that is not null or empty, and then try the command again.
ParameterBindingValidationException: Cannot validate argument on parameter ‘Property’. The argument is null or empty. Provide an argument that is not null or empty, and then try
the command again.
at , : line 126
Describing Container network is created
[+] At least one local container network is available 5.54s
[+] At least one NAT, Transparent, or L2Bridge Network exists 105ms
[+] NAT Network’s vSwitch is internal 68ms
[+] A Windows NAT is configured if a Docker NAT network exists 618ms
[+] Specified Network Gateway IP for NAT network is assigned to Host vNIC 161ms
[+] NAT Network’s internal prefix does not overlap with external IP’ 80ms

I think the error related with Microsoft base images is related with internet connection limitation.

Steps to reproduce the behavior

  1. Install docker as per documentation.
  2. Stop Symantec AV and Windows Firewall
  3. Run hello-world command

Does anyone who encountered this error before? Does it related with the endpoint protection tool?

Thanks for your responses.
Kind regards.