This bug was fixed in the package docker.io - 19.03.8-0ubuntu1.20.04
---
docker.io (19.03.8-0ubuntu1.20.04) focal; urgency=medium
[ Jean-Baptiste Lallement ]
[ Didier Roche ]
* Fix use with ZFS on root:
- docker creates one dataset for any layer of containers that were
SRU verification for Focal:
I have reproduced the problem with docker.io 19.03.8-0ubuntu1 in focal and have
verified that the version of docker.io 19.03.8-0ubuntu1.20.04 in -proposed
fixes the issue.
Marking as verification-done
** Tags removed: verification-needed verification-needed-focal
It seems to me like the wiki page referenced in the SRU should mention
the version of the package which is being SRU'ed not the version of the
package which is in Groovy.
https://github.com/ubuntu/zsys/wiki/Performance-issue-with-docker-on-
ubuntu-20.04-LTS
** Changed in: docker.io (Ubuntu
The new postinst failed for me in groovy, here is the bug I filed:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1882942
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879473
Title:
Here we go: https://github.com/moby/moby/issues/41055
** Bug watch added: github.com/moby/moby/issues #41055
https://github.com/moby/moby/issues/41055
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The "zfs" graph driver is part of Docker itself
(https://github.com/moby/moby/tree/89382f2f20745b9e63bed6c066f104980dff4396/daemon/graphdriver/zfs),
so https://github.com/moby/moby/issues would be the appropriate place to
file an issue (or enhancement request) against it.
--
You received this
If you have the upstream bug report for the ZFS driver (not docker
itself), that would be welcome. I didn’t find anything in the upstream
wiki for the driver which is shipped by default in debian/ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
So yeah, the driver should ideally do the same (create directly under
rpool/), but it really depends on how people layed out their system.
I think in general upstream should clear up their datasets (for stopped
containers), which is more generic.
--
You received this bug notification because
Has this been reported upstream? The fix (in postinst) is large enough
that it seems like something upstream should at least be aware of, and
is probably something they should implement a fix for as well. Do you
think it's something that could/should be fixed in "dockerd" itself?
--
You
This bug was fixed in the package docker.io - 19.03.8-0ubuntu2
---
docker.io (19.03.8-0ubuntu2) groovy; urgency=medium
[ Jean-Baptiste Lallement ]
[ Didier Roche ]
* Fix use with ZFS on root:
- docker creates one dataset for any layer of containers that were
created.
** Also affects: docker.io (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: docker.io (Ubuntu Focal)
Status: New => Triaged
** Changed in: docker.io (Ubuntu Focal)
Importance: Undecided => High
** Changed in: docker.io (Ubuntu Focal)
Assignee:
** Description changed:
[Rationale]
ZFS module of docker creates many snapshots under
/ROOT/machineid/var/lib/. These snapshots are processed by zsys and
lead to timeout.
This patch migrates the snapshots created by docker under the persistent
dataset /var/lib/docker/ so they are
** Description changed:
[Rationale]
- ZFS module of docker creates many snapshots under /var/lib/. These
snapshots are processed by zsys and lead to timeout.
+ ZFS module of docker creates many snapshots under
/ROOT/machineid/var/lib/. These snapshots are processed by zsys and
lead to
13 matches
Mail list logo
