[Bug 1828118] Re: docker tarballs contain /dev/null

[Launchpad Bug Tracker]

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

---------------
livecd-rootfs (2.581) eoan; urgency=medium

  * Remove device nodes later for ubuntu-base:minimized (i.e. docker) builds.
    (LP: #1828118)

 -- Michael Hudson-Doyle <michael.hudson at ubuntu.com>  Wed, 08 May 2019
09:59:35 +1200

** Changed in: livecd-rootfs (Ubuntu)
       Status: In Progress => 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/1828118

Title:
  docker tarballs contain /dev/null

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  New
Status in livecd-rootfs source package in Cosmic:
  New
Status in livecd-rootfs source package in Disco:
  New

Bug description:
  [impact]

  This causes problems for some users as reported in
  https://github.com/tianon/docker-brew-ubuntu-core/issues/62. We don't
  want to regress those users.

  [test case]
  Build a livefs with PROJECT=ubuntu-base SUBPROJECT=minimized. Check that /dev is empty in the resulting tarball.

  [regression potential]
  The change pretty clearly only affects ubuntu-base:minimized builds, so checking that all of /var/cache/apt, /var/lib/apt/lists and /dev are empty should be sufficient, no other build types should regress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1828118/+subscriptions