I'm affected by this bug, too, and I confirm that @raczkow patch solves
the problem
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901648
Title:
docker.io package: cannot stat
I have the same problem with a ZFS-based docker deployment.
The issue in my case seems to be, that
/var/lib/dpkg/info/docker.io.postinst assumes/hard-coded, that the
docker content should be located under the the /var/lib/docker
directory. It then tries to migrate this off into a separate
I've found this bug too.
It fails on postinst script. I've checked it and I'm wondering why does it try
to create zfs dataset when it already exists?
When I applied this patch, everything works OK:
--- /var/lib/dpkg/info/docker.io.postinst.orig 2020-11-08 23:21:14.561453080
+0100
+++
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: docker.io (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901648
Title:
This should probably be filed under the docker.io package instead of
ubuntu-release-upgrader.
** Package changed: ubuntu-release-upgrader (Ubuntu) => docker.io
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.