Comment 4 for bug 1960749

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@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.