mdadm should not run in container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
mdadm is IMHO unneeded in a container.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mdadm 3.3-2ubuntu6
ProcVersionSign
Uname: Linux 4.4.0-18-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Mon Apr 11 14:28:12 2016
MDadmExamine.
MDadmExamine.
MDadmExamine.
MachineType: LENOVO 2516CTO
ProcKernelCmdLine: BOOT_IMAGE=
ProcMDstat:
Personalities :
unused devices: <none>
SourcePackage: mdadm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/14/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET85WW (1.45 )
dmi.board.name: 2516CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 2516CTO
dmi.product.
dmi.sys.vendor: LENOVO
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'
modified.
modified.
This bug was fixed in the package mdadm - 3.3-2ubuntu7
---------------
mdadm (3.3-2ubuntu7) xenial; urgency=medium
* Do not start when inside a container (LP: #1568993)
-- Simon Deziel <email address hidden> Mon, 11 Apr 2016 18:33:45 +0000