Can I use LXD image to create Docker container and/or vice versa?

A container system making use of LXC containers.

the above statement is true for both LXD and Docker. In that case can we use LXD image to create Docker container and/or vice versa?

  • distributed tensorflow using docker
  • remote server returned 400 bad request for apache2 in ubuntu
  • Dockerfile: Docker build can't download packages: centos->yum, debian/ubuntu->apt-get behind intranet
  • Docker SSH or Detach/Attach
  • How to package files with docker image
  • Postgres issue - Ruby on Rails (Postgres) on Google Container Engine
  • Docker container restarting on defining an entrypoint
  • harbor: login required for pulling open image
  • Restrict docker engine to a single GPU
  • Docker, How can I locate the image files after pulling [duplicate]
  • docker build taking too much time in aws ecs
  • Do Docker containers share a single Python GIL?
  • One Solution collect form web for “Can I use LXD image to create Docker container and/or vice versa?”

    They are fundamentally different.

    With LXD container image you get full OS experience, it means all applications and processes that are part of the distro, only kernel is shared with the host. With Docker image you get single process application.

    So you can have Docker running inside LXD container, but not the other way around.

    The confusion might arise from the fact that Docker did use liblxc library in the past, that LXD daemon is using to control containers. If I understand correctly Docker is using another library called libcontainer now to provide isolation.

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