Subject: dpkg: Cannot upgrade some packages on overlayfs: Invalid cross-device link
Date: Wed, 31 Aug 2016 12:16:10 -0300
Package: dpkg
Version: 1.18.10
Severity: normal
Hi,
overlayfs does not support renaming directories when the directories
live in the lower filesystem:
* Directory renames only allowed on "pure upper" (already created on
* upper filesystem, never copied up). Directories which are on lower or
* are merged may not be renamed. For these -EXDEV is returned and
* userspace has to deal with it. This means, when copying up a
* directory we can rely on it and ancestors being stable.
https://github.com/torvalds/linux/blob/v4.8-rc2/fs/overlayfs/copy_up.c#L318-L322
Unfortunately this means that dpkg fails at least in the case where a
directory is converted into a file: apt 1.3~rc2 moves
/usr/share/bug/apt/script to /usr/share/bug/apt . This causes dpkg to
fail when running in an overlayfs with the following error:
# dpkg -i /var/cache/apt/archives/apt_1.3~rc3_amd64.deb
(Reading database ... 11401 files and directories currently installed.)
Preparing to unpack .../archives/apt_1.3~rc3_amd64.deb ...
Unpacking apt (1.3~rc3) over (1.3~rc2) ...
dpkg: error processing archive
/var/cache/apt/archives/apt_1.3~rc3_amd64.deb (--install):
unable to move aside './usr/share/bug/apt' to install new version: Invalid cross-device link
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Processing triggers for libc-bin (2.23-5) ...
Errors were encountered while processing:
/var/cache/apt/archives/apt_1.3~rc3_amd64.deb
I don't know what the correct workaround should be.
This can break pre-build upgrades in sbuild when the schroot is of
overlayfs type.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dpkg depends on:
ii libbz2-1.0 1.0.6-8
ii libc6 2.23-5
ii liblzma5 5.1.1alpha+20120614-2.1
ii libselinux1 2.5-3
ii tar 1.29b-1
ii zlib1g 1:1.2.8.dfsg-2+b1
dpkg recommends no packages.
Versions of packages dpkg suggests:
ii apt 1.3~rc3
-- no debconf information
Acknowledgement sent
to Johannes Schauer <[email protected]>:
Extra info received and forwarded to list. Copy sent to Dpkg Developers <[email protected]>.
(Thu, 01 Sep 2016 07:03:03 GMT) (full text, mbox, link).
Hi,
On Wed, 31 Aug 2016 12:16:10 -0300 Felipe Sateler <[email protected]> wrote:
> overlayfs does not support renaming directories when the directories
> live in the lower filesystem:
>
> * Directory renames only allowed on "pure upper" (already created on
> * upper filesystem, never copied up). Directories which are on lower or
> * are merged may not be renamed. For these -EXDEV is returned and
> * userspace has to deal with it. This means, when copying up a
> * directory we can rely on it and ancestors being stable.
>
> https://github.com/torvalds/linux/blob/v4.8-rc2/fs/overlayfs/copy_up.c#L318-L322
>
> Unfortunately this means that dpkg fails at least in the case where a
> directory is converted into a file: apt 1.3~rc2 moves
> /usr/share/bug/apt/script to /usr/share/bug/apt . This causes dpkg to
> fail when running in an overlayfs with the following error:
>
> # dpkg -i /var/cache/apt/archives/apt_1.3~rc3_amd64.deb
> (Reading database ... 11401 files and directories currently installed.)
> Preparing to unpack .../archives/apt_1.3~rc3_amd64.deb ...
> Unpacking apt (1.3~rc3) over (1.3~rc2) ...
> dpkg: error processing archive
> /var/cache/apt/archives/apt_1.3~rc3_amd64.deb (--install):
> unable to move aside './usr/share/bug/apt' to install new version: Invalid cross-device link
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Processing triggers for libc-bin (2.23-5) ...
> Errors were encountered while processing:
> /var/cache/apt/archives/apt_1.3~rc3_amd64.deb
>
> I don't know what the correct workaround should be.
>
> This can break pre-build upgrades in sbuild when the schroot is of
> overlayfs type.
thanks for the analysis!
I just stumbled across the exact same problem with sbuild in a directory type
overlayfs schroot. My workaround: destroy the chroot (you can now use
sbuild-destroychroot) and then recreate it with sbuild-createchroot. :(
cheers, josch
Acknowledgement sent
to Felipe Sateler <[email protected]>:
Extra info received and forwarded to list. Copy sent to Dpkg Developers <[email protected]>.
(Thu, 01 Sep 2016 11:21:04 GMT) (full text, mbox, link).
On 1 Sep 2016 3:59 a.m., "Johannes Schauer" <[email protected]> wrote:
>
> Hi,
>
> On Wed, 31 Aug 2016 12:16:10 -0300 Felipe Sateler <[email protected]>
wrote:
> > overlayfs does not support renaming directories when the directories
> > live in the lower filesystem:
> >
> > * Directory renames only allowed on "pure upper" (already created on
> > * upper filesystem, never copied up). Directories which are on lower
or
> > * are merged may not be renamed. For these -EXDEV is returned and
> > * userspace has to deal with it. This means, when copying up a
> > * directory we can rely on it and ancestors being stable.
> >
> >
https://github.com/torvalds/linux/blob/v4.8-rc2/fs/overlayfs/copy_up.c#L318-L322
> >
> > Unfortunately this means that dpkg fails at least in the case where a
> > directory is converted into a file: apt 1.3~rc2 moves
> > /usr/share/bug/apt/script to /usr/share/bug/apt . This causes dpkg to
> > fail when running in an overlayfs with the following error:
> >
> > # dpkg -i /var/cache/apt/archives/apt_1.3~rc3_amd64.deb
> > (Reading database ... 11401 files and directories currently installed.)
> > Preparing to unpack .../archives/apt_1.3~rc3_amd64.deb ...
> > Unpacking apt (1.3~rc3) over (1.3~rc2) ...
> > dpkg: error processing archive
> > /var/cache/apt/archives/apt_1.3~rc3_amd64.deb (--install):
> > unable to move aside './usr/share/bug/apt' to install new version:
Invalid cross-device link
> > dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> > Processing triggers for libc-bin (2.23-5) ...
> > Errors were encountered while processing:
> > /var/cache/apt/archives/apt_1.3~rc3_amd64.deb
> >
> > I don't know what the correct workaround should be.
> >
> > This can break pre-build upgrades in sbuild when the schroot is of
> > overlayfs type.
>
> thanks for the analysis!
>
> I just stumbled across the exact same problem with sbuild in a directory
type
> overlayfs schroot. My workaround: destroy the chroot (you can now use
> sbuild-destroychroot) and then recreate it with sbuild-createchroot. :(
You can also enter the source chroot and upgrade there, as that skips the
overlayfs setup. I used sbuild-update and it worked OK.
I discussed this with Guillem on IRC and he doesn't think adding
workarounds for this is reasonable, and this should be fixed in overlayfs.
Assuming a directory lives in the same device as itself seems reasonable to
me, and overlayfs should try hard to pretend it does.
Saludos
Acknowledgement sent
to Raphael Hertzog <[email protected]>:
Extra info received and forwarded to list. Copy sent to Dpkg Developers <[email protected]>.
(Fri, 02 Sep 2016 11:39:04 GMT) (full text, mbox, link).
Subject: Re: Bug#836211: dpkg: Cannot upgrade some packages on overlayfs:
Invalid cross-device link
Date: Fri, 2 Sep 2016 13:36:33 +0200
Hi,
On Wed, 31 Aug 2016, Felipe Sateler wrote:
> overlayfs does not support renaming directories when the directories
> live in the lower filesystem:
[...]
> Unfortunately this means that dpkg fails at least in the case where a
> directory is converted into a file: apt 1.3~rc2 moves
> /usr/share/bug/apt/script to /usr/share/bug/apt . This causes dpkg to
That's the change at the package level. The operation that fails
at the dpkg level is rename('/usr/share/bug/apt', '/usr/share/bug/apt.dpkg-tmp').
> fail when running in an overlayfs with the following error:
[...]
> unable to move aside './usr/share/bug/apt' to install new version: Invalid cross-device link
I got the same failure here but I also saw similar reports in a Kali live
system where overlayfs is used for persistence (and with the upgrade
of gedit). So that error is affecting many Kali users. It's not a
very rare error (ex: https://bugs.kali.org/view.php?id=3473,
https://bugs.kali.org/view.php?id=3476,
https://bugs.kali.org/view.php?id=3361,
https://bugs.kali.org/view.php?id=3365).
I'm putting in copy the overlayfs kernel maintainer... Hello Miklos,
that restriction above (cf
https://github.com/torvalds/linux/blob/v4.8-rc2/fs/overlayfs/copy_up.c#L318-L322)
is very problematic for us.
Do you have plans to get rid of it?
It does not seem very correct to put the burden on user-space to be aware
of overlayfs restrictions such as this one. Renaming a directory is
not something that happens often in practice in the uses cases where
we use overlayfs but it's still frequent enough to deserve better than
a EXDEV error IMO and dpkg trying to rename "foo/" into "foo.dpkg-tmp/"
is in its right to assume that this rename will not cross any device
boundary.
I'm happy to test out kernel patches if I can help you in the process
of getting a fix.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
Acknowledgement sent
to Miklos Szeredi <[email protected]>:
Extra info received and forwarded to list. Copy sent to Dpkg Developers <[email protected]>.
(Fri, 02 Sep 2016 12:33:04 GMT) (full text, mbox, link).
Subject: Re: Bug#836211: dpkg: Cannot upgrade some packages on overlayfs:
Invalid cross-device link
Date: Fri, 2 Sep 2016 14:30:58 +0200
On Fri, Sep 2, 2016 at 1:36 PM, Raphael Hertzog <[email protected]> wrote:
> Hi,
>
> On Wed, 31 Aug 2016, Felipe Sateler wrote:
>> overlayfs does not support renaming directories when the directories
>> live in the lower filesystem:
> [...]
>> Unfortunately this means that dpkg fails at least in the case where a
>> directory is converted into a file: apt 1.3~rc2 moves
>> /usr/share/bug/apt/script to /usr/share/bug/apt . This causes dpkg to
>
> That's the change at the package level. The operation that fails
> at the dpkg level is rename('/usr/share/bug/apt', '/usr/share/bug/apt.dpkg-tmp').
>
>> fail when running in an overlayfs with the following error:
> [...]
>> unable to move aside './usr/share/bug/apt' to install new version: Invalid cross-device link
>
> I got the same failure here but I also saw similar reports in a Kali live
> system where overlayfs is used for persistence (and with the upgrade
> of gedit). So that error is affecting many Kali users. It's not a
> very rare error (ex: https://bugs.kali.org/view.php?id=3473,
> https://bugs.kali.org/view.php?id=3476,
> https://bugs.kali.org/view.php?id=3361,
> https://bugs.kali.org/view.php?id=3365).
>
> I'm putting in copy the overlayfs kernel maintainer... Hello Miklos,
> that restriction above (cf
> https://github.com/torvalds/linux/blob/v4.8-rc2/fs/overlayfs/copy_up.c#L318-L322)
> is very problematic for us.
>
> Do you have plans to get rid of it?
You are the first to report that this quirk actually causes problems
in real life.
I have plans to fix this by adding a "redirector" attribute so that
copied up directories (and perhaps files) can refer to lower directory
that is found at a different ___location relative to the root of the
overlay from the ___location of the upper directory.
Maybe an example can make this more clear:
lower/foo/bar/baz
upper/foo/bar <- whiteout
upper/moved/here <- redirects to "foo/bar"
will result in the tree:
overlay/moved/here/baz
> It does not seem very correct to put the burden on user-space to be aware
> of overlayfs restrictions such as this one. Renaming a directory is
> not something that happens often in practice in the uses cases where
> we use overlayfs but it's still frequent enough to deserve better than
> a EXDEV error IMO and dpkg trying to rename "foo/" into "foo.dpkg-tmp/"
> is in its right to assume that this rename will not cross any device
> boundary.
The EXDEV trick just works for mv(1), hence this didn't seem to be a
big issue in practice.
Thanks,
Miklos
Acknowledgement sent
to Guillem Jover <[email protected]>:
Extra info received and forwarded to list. Copy sent to Dpkg Developers <[email protected]>.
(Fri, 02 Sep 2016 13:06:07 GMT) (full text, mbox, link).
Subject: Re: Bug#836211: dpkg: Cannot upgrade some packages on overlayfs:
Invalid cross-device link
Date: Fri, 2 Sep 2016 15:03:54 +0200
Hi!
On Fri, 2016-09-02 at 14:30:58 +0200, Miklos Szeredi wrote:
> You are the first to report that this quirk actually causes problems
> in real life.
>
> I have plans to fix this by adding a "redirector" attribute so that
> copied up directories (and perhaps files) can refer to lower directory
> that is found at a different ___location relative to the root of the
> overlay from the ___location of the upper directory.
>
> Maybe an example can make this more clear:
>
> lower/foo/bar/baz
> upper/foo/bar <- whiteout
> upper/moved/here <- redirects to "foo/bar"
>
> will result in the tree:
>
> overlay/moved/here/baz
That'd be very much appreciated, thanks!
> > It does not seem very correct to put the burden on user-space to be aware
> > of overlayfs restrictions such as this one. Renaming a directory is
> > not something that happens often in practice in the uses cases where
> > we use overlayfs but it's still frequent enough to deserve better than
> > a EXDEV error IMO and dpkg trying to rename "foo/" into "foo.dpkg-tmp/"
> > is in its right to assume that this rename will not cross any device
> > boundary.
>
> The EXDEV trick just works for mv(1), hence this didn't seem to be a
> big issue in practice.
In dpkg, the directory is rename(2)d to perform an atomic temporary backup,
so that it can be rolled-back in case of errors during unpacking. Having to
possibly do a deep-copy and a deep-remove, and then trying to recover from
errors inbetween those, would be very unsatisfactory.
Thanks,
Guillem
Acknowledgement sent
to Raphael Hertzog <[email protected]>:
Extra info received and forwarded to list. Copy sent to Dpkg Developers <[email protected]>.
(Fri, 02 Sep 2016 14:51:07 GMT) (full text, mbox, link).
Hi,
On Wed, 31 Aug 2016, Felipe Sateler wrote:
> I don't know what the correct workaround should be.
Just for the record, the attached patch is what we use in Kali
to work-around this problem. It works but it's not going to be merged in
Debian because we really want a fix at the overlayfs level instead
(and this is just a hack relying on "mv" to copy the whole-directory).
I post it just in case other derivatives have a similar need.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
Acknowledgement sent
to Miklos Szeredi <[email protected]>:
Extra info received and forwarded to list. Copy sent to Dpkg Developers <[email protected]>.
(Mon, 05 Sep 2016 08:33:04 GMT) (full text, mbox, link).
Acknowledgement sent
to Guillem Jover <[email protected]>:
Extra info received and forwarded to list. Copy sent to Dpkg Developers <[email protected]>.
(Sat, 17 Sep 2016 15:39:04 GMT) (full text, mbox, link).
Subject: Re: Bug#836211: dpkg: Cannot upgrade some packages on overlayfs:
Invalid cross-device link
Date: Sat, 17 Sep 2016 17:36:09 +0200
Control: reassign -1 linux
Control: affects -1 dpkg
Hi!
[ Reassigning to linux, where this can be fixed. Upstream has provided
a preliminary patch to this bug report, which might need testing and
perhaps some polishing? Trimmed irrelevant information. ]
On Wed, 2016-08-31 at 12:16:10 -0300, Felipe Sateler wrote:
> Package: dpkg
> Version: 1.18.10
> Severity: normal
> overlayfs does not support renaming directories when the directories
> live in the lower filesystem:
>
> * Directory renames only allowed on "pure upper" (already created on
> * upper filesystem, never copied up). Directories which are on lower or
> * are merged may not be renamed. For these -EXDEV is returned and
> * userspace has to deal with it. This means, when copying up a
> * directory we can rely on it and ancestors being stable.
>
> https://github.com/torvalds/linux/blob/v4.8-rc2/fs/overlayfs/copy_up.c#L318-L322
>
> Unfortunately this means that dpkg fails at least in the case where a
> directory is converted into a file: apt 1.3~rc2 moves
> /usr/share/bug/apt/script to /usr/share/bug/apt . This causes dpkg to
> fail when running in an overlayfs with the following error:
>
> # dpkg -i /var/cache/apt/archives/apt_1.3~rc3_amd64.deb
> (Reading database ... 11401 files and directories currently installed.)
> Preparing to unpack .../archives/apt_1.3~rc3_amd64.deb ...
> Unpacking apt (1.3~rc3) over (1.3~rc2) ...
> dpkg: error processing archive
> /var/cache/apt/archives/apt_1.3~rc3_amd64.deb (--install):
> unable to move aside './usr/share/bug/apt' to install new version: Invalid cross-device link
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Processing triggers for libc-bin (2.23-5) ...
> Errors were encountered while processing:
> /var/cache/apt/archives/apt_1.3~rc3_amd64.deb
>
> I don't know what the correct workaround should be.
>
> This can break pre-build upgrades in sbuild when the schroot is of
> overlayfs type.
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable-debug
> APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Thanks,
Guillem
Subject: Re: Bug#836211: dpkg: Cannot upgrade some packages on overlayfs:
Invalid cross-device link
Date: Fri, 25 Aug 2017 21:34:32 +0200
Version: 4.10.0-1~exp1
On Sat, 17 Sep 2016, Guillem Jover wrote:
> [ Reassigning to linux, where this can be fixed. Upstream has provided
> a preliminary patch to this bug report, which might need testing and
> perhaps some polishing? Trimmed irrelevant information. ]
I verified today that the issue is gone with Linux 4.12 and apparently
the appropriate patches have been merged for Linux 4.10 already (merged by
linus in commit ff0f962ca3c38239b299a70e7eea27abfbb979c3).
So I'm closing this bug.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/
Acknowledgement sent
to Raphael Hertzog <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <[email protected]>.
(Mon, 04 Sep 2017 13:03:03 GMT) (full text, mbox, link).
Subject: Re: Bug#836211: dpkg: Cannot upgrade some packages on overlayfs:
Invalid cross-device link
Date: Mon, 4 Sep 2017 15:01:26 +0200
Control: reopen -1
Control: notfixed -1 4.10.0-1~exp1
Control: found -1 4.12.6-1
On Fri, 25 Aug 2017, Raphael Hertzog wrote:
> I verified today that the issue is gone with Linux 4.12 and apparently
> the appropriate patches have been merged for Linux 4.10 already (merged by
> linus in commit ff0f962ca3c38239b299a70e7eea27abfbb979c3).
I don't know how I did my check last time, but I was wrong. The changes
merged above fixed issues about tools being confused with the unexpected
st_dev values on files but they did not fix the fact that overlayfs
might return EXDEV when renaming a directory that is part of the lower
layer.
So I'm opening the bug again.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/
Acknowledgement sent
to Salvatore Bonaccorso <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <[email protected]>.
(Sun, 02 May 2021 07:09:04 GMT) (full text, mbox, link).
Subject: Re: Bug#836211: dpkg: Cannot upgrade some packages on overlayfs:
Invalid cross-device link
Date: Sun, 2 May 2021 09:06:49 +0200
Hi,
On Mon, Sep 04, 2017 at 03:01:26PM +0200, Raphael Hertzog wrote:
> Control: reopen -1
> Control: notfixed -1 4.10.0-1~exp1
> Control: found -1 4.12.6-1
>
> On Fri, 25 Aug 2017, Raphael Hertzog wrote:
> > I verified today that the issue is gone with Linux 4.12 and apparently
> > the appropriate patches have been merged for Linux 4.10 already (merged by
> > linus in commit ff0f962ca3c38239b299a70e7eea27abfbb979c3).
>
> I don't know how I did my check last time, but I was wrong. The changes
> merged above fixed issues about tools being confused with the unexpected
> st_dev values on files but they did not fix the fact that overlayfs
> might return EXDEV when renaming a directory that is part of the lower
> layer.
>
> So I'm opening the bug again.
Doing some maintenance on open kernel bugs. Is this by now still an
issue with recent kernels? If not can we close this bug? Part of the
isuses at leas were fixed in 4.10.0-1~exp1, but what about the
remaining or followup issue mentioned by Raphael?
Regards,
Salvatore
Acknowledgement sent
to Nicolas Schier <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <[email protected]>.
(Fri, 21 May 2021 10:18:03 GMT) (full text, mbox, link).
Hi,
On Sun 02 May 2021 09:06:49 GMT, Salvatore Bonaccorso wrote:
> Hi,
>
> On Mon, Sep 04, 2017 at 03:01:26PM +0200, Raphael Hertzog wrote:
> > Control: reopen -1
> > Control: notfixed -1 4.10.0-1~exp1
> > Control: found -1 4.12.6-1
> >
> > On Fri, 25 Aug 2017, Raphael Hertzog wrote:
> > > I verified today that the issue is gone with Linux 4.12 and apparently
> > > the appropriate patches have been merged for Linux 4.10 already (merged by
> > > linus in commit ff0f962ca3c38239b299a70e7eea27abfbb979c3).
> >
> > I don't know how I did my check last time, but I was wrong. The changes
> > merged above fixed issues about tools being confused with the unexpected
> > st_dev values on files but they did not fix the fact that overlayfs
> > might return EXDEV when renaming a directory that is part of the lower
> > layer.
> >
> > So I'm opening the bug again.
>
> Doing some maintenance on open kernel bugs. Is this by now still an
> issue with recent kernels? If not can we close this bug? Part of the
> isuses at leas were fixed in 4.10.0-1~exp1, but what about the
> remaining or followup issue mentioned by Raphael?
>
> Regards,
> Salvatore
the EXDEV return value is still reproducible:
$ mkdir -p /tmp/ovl/{lower/dir,upper,work,mount}
$ sudo mount -t overlay -o lowerdir=/tmp/ovl/lower,upperdir=/tmp/ovl/upper,workdir=/tmp/ovl/work none /tmp/ovl/mount
$ strace -e trace=rename,renameat,renameat2 mv /tmp/ovl/mount/dir /tmp/ovl/mount/newname
renameat2(AT_FDCWD, "/tmp/ovl/mount/dir", AT_FDCWD, "/tmp/ovl/mount/newname", RENAME_NOREPLACE) = -1 EXDEV (Invalid cross-device link)
+++ exited with 0 +++
and in dpkg sources I cannot find any special handling for EXDEV. From
my point of view, the bug is still not fixed.
Kind regards,
Nicolas
Acknowledgement sent
to Tomas Krizek <[email protected]>:
Extra info received and forwarded to list. Copy sent to Debian Kernel Team <[email protected]>.
(Mon, 07 Jun 2021 14:30:03 GMT) (full text, mbox, link).
On Wed, 31 Aug 2016 12:16:10 -0300 Felipe Sateler <[email protected]>
wrote:> unable to move aside './usr/share/bug/apt' to install new
version: Invalid cross-device link
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
I'm hitting this bug when attempting to use debian in a container backed
by overlayfs.
Kernel version on host: 5.12.8.arch1-1
It works fine with kernel 5.10.41-1.
--
Tomas Krizek
PGP: 4A8B A48C 2AED 933B D495 C509 A1FB A5F7 EF8C 4869
Debbugs is free software and licensed under the terms of the GNU General
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.