In preparation to run VM’s on our IBM SAN we attempted running Docker on a Proxmox container which was running Debian 9. During the Docker install everything went smoothly following dockers instructions found here: (https://docs.docker.com/install/linux/docker-ce/debian/). But when I tried to run Docker’s hello-world image the following errors were reported….
$ docker run hello-world
Unable to find image ‘hello-world:latest’ locally
The local check for hello-world worked as it should and failed to find the image.
latest: Pulling from library/hello-world
1b930d010525: Already exists
Status: Downloaded newer image for hello-world:latest
Docker successfully downloaded hello-world image from the DockerHub.
But the image would not run as a container due to this error.
docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused “process_linux.go:449: container init caused \”rootfs_linux.go:58: mounting \\\”proc\\\” to rootfs \\\”/var/lib/docker/vfs/dir/d6d59e3683464d545a8161a8b0a8162022b7b8af9917e8cc802d55492c3dac37\\\” at \\\”/proc\\\” caused \\\”permission denied\\\”\””: unknown.
ERRO error waiting for container: context canceled
Searching online it seems many people have had this issue or error codes that are very similar. Several people had posted solutions, from changing permissions to creating new directories to mount or editing config files, but none of these fixed the issue on our setup.
The solution was incredibly simple and stemmed from the very beginning when I created a Linux (Debian9) VM to install Docker on. Using Proxmox I had created a container not a VM to cut down on resource usage. Being as Docker was now trying to create containers within containers the option for Nesting must be selected with in the Options -> Features section of the Proxmox container.
Once Nesting had been selected, docker ran flawlessly.