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

Bug #1645468 reported by Tianon Gravi
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
cloud-images
New
Undecided
Dan Watkins
livecd-rootfs (Ubuntu)
Fix Released
Undecided
Unassigned

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? :)

Related branches

Changed in cloud-images:
assignee: nobody → Dan Watkins (daniel-thewatkins)
milestone: none → z-2016-12-01
Dan Watkins (oddbloke)
Changed in cloud-images:
milestone: z-2016-12-01 → z-2016-12-15
tags: added: id-586e3c15a4f68ac01d23153a
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Thu, 27 Sep 2018 15:21:49 -0700

Changed in livecd-rootfs (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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