[Bug 1645468] Re: having /dev in partner-images/Docker is redundant (and causes issues when using user namespaces)

[Launchpad Bug Tracker]

This bug was fixed in the package livecd-rootfs - 2.541

---------------
livecd-rootfs (2.541) cosmic; urgency=medium

  [ Michael Hudson-Doyle ]
  * Remove device nodes from Docker images. (LP: #1645468)

  [ Robert C Jennings ]
  * Add the server snap seed to the ubuntu-cpc project
  * Allow hooks to replace generic snap assertion

 -- Steve Langasek <steve.langasek at ubuntu.com>  Thu, 27 Sep 2018
15:21:49 -0700

** Changed in: livecd-rootfs (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1645468

Title:
  having /dev in partner-images/Docker is redundant (and causes issues
  when using user namespaces)

Status in cloud-images:
  New
Status in livecd-rootfs package in Ubuntu:
  Fix Released

Bug description:
  As noted in https://github.com/tianon/docker-brew-ubuntu-
  core/issues/62, having "/dev" contents included in the partner-images
  rootfs tarballs causes issues with user namespaces, and is redundant
  given that Docker will always mount a trimmed "/dev" on top of
  whatever the image provides.

  Any chance we could get "/dev" removed during the tarball build
  process? :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1645468/+subscriptions