[Bug 1960749] Re: dpkg incorrectly installs singular-doc in jammy Docker container

[Julian Andres Klode]

Yes, lxd containers are full-fledged system containers which also target
interactive users. The focus of the docker community is vastly
different, focusing on the smallest possible containers:

https://ubuntu.com/blog/minimal-ubuntu-released

It's odd you end up with anything inside /usr/share/doc, does dpkg still
extract excluded symlinks? This needs further investigation.

Changing dpkg -V, I don't know, maybe, it seems to support an error
message for "missing"

** Changed in: dpkg (Ubuntu)
       Status: Invalid => New

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

Title:
  dpkg incorrectly installs singular-doc in jammy Docker container

Status in dpkg package in Ubuntu:
  Triaged

Bug description:
  Also reported on https://github.com/tianon/docker-brew-ubuntu-
  core/issues/230

  Using official Jammy image in Docker (macOS) and Podman (Fedora).
  In both cases, using CLI in the image and running

  apt install singular-doc
  dpkg -V singular-doc
  reports a lot of missing files. In fact, the only present files are dangling links to missing files in the package.
  The package itself is not broken - extracting it in Jammy not in Docker/Podman (say, in an lxc container) works.
  And extracting it in Debian/bookworm CLI run in Docker works too.

  As well, the same behaviour is observed using the corresponding
  singular-doc_4.2.1-p3+ds-1_all.deb file, and installing it using dpkg
  -i. This points to dpkg as the culprit.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1960749/+subscriptions