Top post:
try installing usr-is-merged after changing sources.list before
anything else.
If that works and nobody else chimes in first I'll explain what is going
on.
(may or may not work, no time to check now)
Tim.
On Fri, 28 Oct 2022, Tim Woodall wrote:
On Thu, 27 Oct 2022, Hogren wrote:
Anybody can help me or confirm me that it?s a bug and I need to open a bug
issue ?
#9 28.26 Preparing to unpack .../archives/usrmerge_33_all.deb ...
#9 28.28 Unpacking usrmerge (33) ...
#9 28.32 Setting up usrmerge (33) ...
#9 28.42 Warning: overlayfs detected, /usr/lib/usrmerge/convert-usrmerge
will not
#9 28.42 be run automatically. See #1008202 for details.
#9 28.42
#9 28.42 If this is a container then it can be converted by unpacking the
image,
#9 28.42 entering it with chroot(8), installling usrmerge and then
repacking the
#9 28.42 image again. at /usr/lib/usrmerge/convert-usrmerge line 399.
#9 28.42 E: usrmerge failed.
#9 28.42 dpkg: error processing package usrmerge (--configure):
#9 28.42 installed usrmerge package post-installation script subprocess
returned error exit status 1
#9 28.44 Errors were encountered while processing:
#9 28.44 usrmerge
#9 28.46 E: Sub-process /usr/bin/dpkg returned an error code (1)
------
executor failed running [/bin/sh -c apt upgrade -y]: exit code: 100
I don't know much about docker containers and I only know enough about
usrmerge to avoid it causing me issues on my own installer but I believe
this is 'working as designed'
The problem is that usrmerge needs to move /{bin,sbin,lib} to /usr/ and
then create compatibility symlinks. But because you're using an
overlayfs it cannot properly do that - it needs the underlying RO system
changed.
So, unpack the underlying fs, install usrmerge (if you want, remove it
again and its dependencies, install usr-is-merged[1]) repack, and then
try again.
[1] if you're starting from bullseye then usr-is-merged isn't available
so either you have to start with bookworm or accept the usrmerge
dependencies in the underlying fs (or backport usr-is-merged)
