https://bugzilla.redhat.com/show_bug.cgi?id=1026976
Bug ID: 1026976
Summary: "Error starting container, Error adding device, can't
find device for parent ''" when starting fedora docker
image
Product: Fedora
Version: 19
Component: docker-io
Assignee: l...@redhat.com
Reporter: sjenn...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: golang@lists.fedoraproject.org, l...@redhat.com,
mat...@redhat.com, mgold...@redhat.com,
vba...@redhat.com
Description of problem:
Running container fails with:
Error: Error starting container 43e36bc82ecd: Error adding device for
'0f3e92b4e94d643339d14b096ade73b42b28ff6f9be99064696a97f248c1a651': can't find
device for parent ''
Additionally /var/log/messages has this:
Nov 5 10:20:20 docker kernel: [ 85.389079] device-mapper: space map common:
index_check failed: blocknr 0 != wanted 314
Nov 5 10:20:20 docker kernel: [ 85.389102] device-mapper: block manager:
index validator check failed for block 314
Nov 5 10:20:20 docker kernel: [ 85.389284] device-mapper: transaction
manager: couldn't open metadata space map
Nov 5 10:20:20 docker kernel: [ 85.389295] device-mapper: thin metadata:
tm_open_with_sm failed
Nov 5 10:20:20 docker kernel: [ 85.390964] device-mapper: table: 253:1:
thin-pool: Error creating metadata object
Nov 5 10:20:20 docker kernel: [ 85.391095] device-mapper: ioctl: error
adding target to table
Version-Release number of selected component (if applicable):
# rpm -qa docker-io
docker-io-0.7-0.13.dm.fc19.x86_64
# uname -a
Linux ... 3.11.6-200.fc19.x86_64 #1 SMP Fri Oct 18 22:34:18 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
How reproducible:
Every time
Steps to Reproduce:
1. Install docker-io-0.7-0.13.dm.fc19.x86_64.rpm
2. Start docker daemon (docker -d &)
3. Download mattdm/fedora images (docker pull mattdm/fedora)
4. Try to start a fedora image (docker run -i -t mattdm/fedora /bin/bash)
Actual results:
Error: Error starting container 96c6d2706331: Error adding device for
'0f3e92b4e94d643339d14b096ade73b42b28ff6f9be99064696a97f248c1a651': can't find
device for parent ''
Expected results:
Shell access to fedora container
Additional info:
My rootfs is on an LV fedora-root in VG fedora
# dmsetup ls --tree
fedora-root (253:0)
└─ (252:2)
Not sure if that would make a difference.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
golang mailing list
golang@lists.fedoraproject.org
https://lists.fedoraproject.org/mailman/listinfo/golang
