Privileged Docker container in privileged LXD container

Bug #1599121 reported by blockmurder on 2016-07-05
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Fix Released
Unknown (Ubuntu)

Bug Description

Issue description:

Trying to run privileged docker container in a privileged LXD container. Goal would be to run a rancher/agent:v1.0.2 container, but it does not work with ubuntu:latest either.

Steps to reproduce:

Run a container (ubuntu:16.04, privileged) with instructions found here:

Apply lxc profile device add docker tuntap unix-char path=/dev/net/tun to fix issue discussed here:

Run docker run -d --name test --privileged ubuntu:latest which produces the following output:
docker: Error response from daemon: Container command not found or does not exist..

Tested with 1.10.3 and 1.11.2(proposed), unprivileged Docker containers running fine...

This bug has been filed on LXD github repository as well:

LXD Host:
DistroRelease: Ubuntu 14.04 LTS 4.4.0-28-generic
Package: lxd 2.0.2-0ubuntu1~16.04.1

Docker container:
DistroRelease: Ubuntu 14.04 LTS 4.4.0-28-generic
Package: 1.10.3-0ubuntu6

blockmurder (5-gnfo-m) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in (Ubuntu):
status: New → Confirmed
Anibal Rivero (anibalrivero) wrote :

LXD Host:
DistroRelease: Ubuntu 16.04 LTS 4.4.0-22-generic
Package: lxd
Version: 2.0.0-0ubuntu4

Version: 1.10.3-0ubuntu6

Velkan (velkan-s) wrote :

Similar with 1.12.6-0ubuntu1~16.04.1.

Linked back the LXD issue that was filed as a bug task to get auto-tracking.
But FYI - the status there is to currently wait on docker packaging expertise from here.

Changed in lxd:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.