Docker image fails to create netlink handle

Can anyone help me make sense of the below error and others like it? I’ve Googled around, but nothing makes sense for my context. I download my Docker Image, but the container refuses to start. The namespace referenced is not always 26, but could be anything from 20-29. I am launching my Docker container onto an EC2 instance and pulling the image from AWS ECR. The error is persistent no matter if I re-launch the instance completely or restart docker.

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-05-
11T21:00:18Z\\\" level=fatal msg=\\\"failed to create a netlink handle: 
failed to set into network namespace 26 while creating netlink socket: 
invalid argument\\\" \\n\"".

  • stop a database container in docker automatically
  • Different development environments with docker
  • Boot2Docker to Google Compute Engine VM: saving Docker container
  • Updating kubectl with new configurations
  • Update k8s ConfigMap or Secret without deleting the existing one
  • Why is ARG in a DOCKERFILE not recommended for passing secrets?
  • Artifactory docker Repository overrides released docker artifacts
  • Symfony 3 and Docker (nginx, php7.1-fpm mysql8) Performances low on Windows
  • Moving files into a Docker Data Volume
  • How to share static data among different containers or can we share the cache'd data among containers?
  • Enable external network access from my docker swarm
  • What is the location of config file in Docker 1.9?
  • One Solution collect form web for “Docker image fails to create netlink handle”

    Did you try running it with the --privileged option?

    If it still doesn’t run, try adding --security-opts seccomp=unconfined and either --security-opts apparmor=unconfined or --security-opts selinux=unconfined depending whether you’re running Ubuntu or a distribution with SELinux enabled, respectively.

    If it works, try substituting the --privileged option with –cap-add=NET_ADMIN` instead, as running containers in privileged mode is discouraged for security reasons.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.