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

[Dima Pasechnik]

This was discovered during the run of a CI, and interactive steps are
provided for the ease of reproduction, not because it's the way it was
found. If you don't know how to use Docker images interactively, it
doesn't mean they are not used this way.

Also, even if I'd agree that Docker containers are useless for interactive work (I don't) note that the steps still install broken symbolic links into /usr/share/doc.
One sees

# ls -l /usr/share/doc/singular/html/
total 0
lrwxrwxrwx 1 root root 13 Dec 17 20:20 sing_1068.png -> sing_1008.png
...
root at c9df22f5e5ab:/sage# ls -l /usr/share/doc/singular/html/ | wc -l
71


And I really think that it's up to the user to decide how to use Docker containers, and you should not break things like this. By the way, Jammy lxc container does not show this bug - are you telling me that lxc images are OK for interactive work, but Docker containers are not?


Containers/images are very useful for quick testing of whatever pops up, and breaking system packages like this is very bad.

I wasted a day chasing this weirdness up - dpkg should at the very least
emit a warning that it drops things in such a case.

-- 
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:
  Invalid

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