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

[Launchpad Bug Tracker]

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

---------------
livecd-rootfs (2.525.23) bionic; urgency=medium

  * Backport two minimizations for the docker images: remove apt lists that
    are removed downstream anyway, and remove device nodes from the image.
    (LP: #1828118)

livecd-rootfs (2.525.22) bionic; urgency=medium

  * Subiquity specific changes SRU LP: #1827357
    - subiquity: make subiquity_config.mount optional
    - Make serial-subiquity@ use the same codepath as tty1 subiquity.
    - Fix ubuntu-server-live images to generate initrd with casper UUID.

 -- Michael Hudson-Doyle <michael.hudson at ubuntu.com>  Wed, 08 May 2019
10:48:39 +1200

** Changed in: livecd-rootfs (Ubuntu Bionic)
       Status: Fix Committed => 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:
  Fix Released
Status in livecd-rootfs source package in Cosmic:
  Fix Released
Status in livecd-rootfs source package in Disco:
  Fix Released

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