Turns out we need to explicitly list --privileged in addition to the other
flags. Here's how it runs now:

docker run --name deis-store-volume --rm -e HOST=$COREOS_PRIVATE_IPV4 --net
host --privileged -v /dev:/dev -v /sys:/sys -v /data:/data $IMAGE


*Chris Armstrong*Head of Services
OpDemand / Deis.io

GitHub: https://github.com/deis/deis -- Docs: http://docs.deis.io/


On Thu, Oct 9, 2014 at 1:47 PM, Christopher Armstrong <[email protected]>
wrote:

> So I can successfully map within the container, but when I try to
> `mkfs.ext4 -m0 /dev/rbd0` I get:
>
> Oct 09 19:31:03 deis-2 sh[1569]: mke2fs 1.42.9 (4-Feb-2014)
> Oct 09 19:31:03 deis-2 sh[1569]: mkfs.ext4: Operation not permitted while
> trying to determine filesystem size
>
> Once the device is mapped within the container, though, I can successfully
> format the volume on the host.
>
>
> *Chris Armstrong*Head of Services
> OpDemand / Deis.io
>
> GitHub: https://github.com/deis/deis -- Docs: http://docs.deis.io/
>
>
> On Thu, Oct 9, 2014 at 11:54 AM, Christopher Armstrong <[email protected]
> > wrote:
>
>> Adding `-v /dev:/dev` works as expected - after mapping, the device shows
>> up as /dev/rbd0. Agreed, though - I thought --privileged should do this.
>>
>>
>> *Chris Armstrong*Head of Services
>> OpDemand / Deis.io
>>
>> GitHub: https://github.com/deis/deis -- Docs: http://docs.deis.io/
>>
>>
>> On Thu, Oct 9, 2014 at 11:36 AM, Ilya Dryomov <[email protected]>
>> wrote:
>>
>>> On Thu, Oct 9, 2014 at 9:23 PM, Christopher Armstrong
>>> <[email protected]> wrote:
>>> > Good point. I'll have to play around with it - was just excited to get
>>> past
>>> > the blocking map issue.
>>>
>>> This could be a docker bug - my understanding is that all devices have
>>> to show up if running with --privileged, which I do on my test box.
>>> I'll poke around some more as well.
>>>
>>> Thanks,
>>>
>>>                 Ilya
>>>
>>
>>
>
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Reply via email to