moby: Failed to create a netlink handle: failed to set into network namespace xx while creating netlink socket
BUG REPORT INFORMATION
Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST –>
Description No container will start due to a failure to initialize the socket.
When a docker image is pulled, attempting to run/start it yields:
docker: Error response from daemon: oci runtime error: container_linux.go:247: starting container process caused “process_linux.go:334: running prestart hook 0 caused "error running hook: exit status 1, stdout: , stderr: time=\"2017-06-13T13:05:42Z\" level=fatal msg=\"failed to create a netlink handle: failed to set into network namespace 21 while creating netlink socket: invalid argument\" \n"”.
Steps to reproduce the issue:
- Download image
- Attempt to start any container with sudo docker run, even hello-world
Describe the results you received:
Container will not start
Describe the results you expected:
Container should start with no issues.
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version
:
Client:
Version: 17.03.1-ce
API version: 1.27
Go version: go1.7.5
Git commit: c6d412e
Built: Mon Mar 27 17:14:09 2017
OS/Arch: linux/amd64
Server:
Version: 17.03.1-ce
API version: 1.27 (minimum version 1.12)
Go version: go1.7.5
Git commit: c6d412e
Built: Mon Mar 27 17:14:09 2017
OS/Arch: linux/amd64
Experimental: false
Output of docker info
:
Containers: 13
Running: 0
Paused: 0
Stopped: 13
Images: 2
Server Version: 17.03.1-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 4ab9917febca54791c5f071a9d1f404867857fcc
runc version: 54296cf40ad8143b62dbcaa1d90e520a2136ddfe
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.4.0-78-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.795 GiB
Name: ip-10-11-5-206
ID: VRSZ:FZGN:B2CZ:7CGR:36PM:RDXC:KB3I:ET4N:ZPX6:4BOH:7S7O:RFRU
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Http Proxy: http://awsprodproxy.company.net:3128/
Https Proxy: http://awsprodproxy.company.net:3128/
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Additional environment details (AWS, VirtualBox, physical, etc.): Running on AWS EC2 and pulling image from AWS ECR, Ubuntu 16.04 image.
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 18 (6 by maintainers)
I just hit the same issue.
Ubuntu 16.04.3 LTS (vmware vm )
docker version
when I run container it alway error
My IT support suggest me to stop ds_agent service.
I do
and run container again. It work for me.