lvmetad should not run in container
Bug #1568954 reported by
Simon Déziel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| lvm2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
lvmetad is IMHO unneeded in a container.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lvm2 2.02.133-1ubuntu8
ProcVersionSign
Uname: Linux 4.4.0-18-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Apr 11 12:23:27 2016
SourcePackage: lvm2
UpgradeStatus: No upgrade log present (probably fresh install)
Revision history for this message
| Simon Déziel (sdeziel) wrote | #1 |
Revision history for this message
| Simon Déziel (sdeziel) wrote | #2 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in lvm2 (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package lvm2 - 2.02.133-1ubuntu9
---------------
lvm2 (2.02.133-1ubuntu9) xenial; urgency=medium
* Do not start when inside a container (LP: #1568954)
-- Simon Deziel <email address hidden> Mon, 11 Apr 2016 18:21:59 +0000