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\"".

  • Logs not generated in docker compose
  • How to tunnel to into the private network of my docker containers on Bluemix?
  • Which file stores the docker image dependencies?
  • Can you add initial data to a volume in Docker that is available on pull?
  • docker container ssl certificates
  • Cross-compile using go build CGO_ENABLED - warning: libudev.so.1 not found
  • How do I not create docker container logs?
  • Docker temporary files strategy
  • Passenger Still Runs in Production Despite Everything Seeming to Be Correct?
  • docker support visual studio 2017 fails
  • Docker run error: could not create session key: too many links
  • AWT error while trying to build Jenkins Docker image based on Alpine -
  • 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.