Hi there, while being successful with the patched Ubuntu 16.04 docker.io package I am not able to run the latest edge version of docker (17.10.0-ce, build f4ffd25) in an LXD (2.18) container:
root@optimal-flounder:~# docker --version Docker version 17.10.0-ce, build f4ffd25 root@optimal-flounder:~# docker run hello-world container_linux.go:295: starting container process caused "process_linux.go:399: container init caused \"rootfs_linux.go:57: mounting \\\"proc\\\" to rootfs \\\"/var/lib/docker/vfs/dir/23c1046e684604b6d120c0fd1fa7e3526e134a7927631efab9ab4dc3d7456f6d\\\" at \\\"/proc\\\" caused \\\"permission denied\\\"\"" docker: Error response from daemon: oci runtime error: container_linux.go:295: starting container process caused "process_linux.go:399: container init caused \"rootfs_linux.go:57: mounting \\\"proc\\\" to rootfs \\\"/var/lib/docker/vfs/dir/23c1046e684604b6d120c0fd1fa7e3526e134a7927631efab9ab4dc3d7456f6d\\\" at \\\"/proc\\\" caused \\\"permission denied\\\"\"". ERRO[0000] error waiting for container: context canceled Is this a new issue or are these patches still missing? https://github.com/moby/moby/pulls?q=is%3Apr+hallyn https://github.com/opencontainers/runc/pulls?q=is%3Apr+hallyn It seems that the mount.Root patch was never merged although the pull request was closed. Are there plans to maintain the possibility of running docker inside an LXD container as a feature? Or is this just a proof of concept for docker 1.12? Any idea how upstream developers see this? Personally I think it is a killer feature to use LXD for docker deployment instead of VMs. It would be a pity if docker on LXD turns out as a nine day wonder. Cheers, Björn _______________________________________________ lxc-users mailing list lxc-users@lists.linuxcontainers.org http://lists.linuxcontainers.org/listinfo/lxc-users