On Fri, Oct 10, 2014 at 12:09 AM, Christopher Armstrong
wrote:
> 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
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 / Dei
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 wi
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:3
On Thu, Oct 9, 2014 at 9:23 PM, Christopher Armstrong
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 tes
Good point. I'll have to play around with it - was just excited to get past
the blocking map issue.
*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:20 AM, Ilya Dryomov
wrote:
> On Thu, Oct 9, 20
On Thu, Oct 9, 2014 at 8:34 PM, Christopher Armstrong
wrote:
> Hey guys,
>
> Good news!! Ilya investigated the ticket and gave me a hint as to the issue
> - we need to use `--net host` on the consuming container so that the network
> context is what Ceph expects. I am now running my test container
Hey guys,
Good news!! Ilya investigated the ticket and gave me a hint as to the issue
- we need to use `--net host` on the consuming container so that the
network context is what Ceph expects. I am now running my test container
like so:
docker run -i -v /sys:/sys --net host
172.21.12.100:5000/dei
Thank you Ilya! Please let me know if I can help. To give you some
background, I'm one of the core maintainers of Deis, an open-source PaaS
built on Docker and CoreOS. We have Ceph running quite successfully as
implemented in https://github.com/deis/deis/pull/1910 based on Seán
McCord's containeriz
On Tue, Oct 7, 2014 at 9:46 AM, Christopher Armstrong
wrote:
> Hi folks,
>
> I'm trying to gather additional information surrounding
> http://tracker.ceph.com/issues/9355 so we can hopefully find the root of
> what's preventing us from successfully mapping RBD volumes inside a Linux
> container.
>
Hi folks,
I'm trying to gather additional information surrounding
http://tracker.ceph.com/issues/9355 so we can hopefully find the root of
what's preventing us from successfully mapping RBD volumes inside a Linux
container.
With the RBD kernel module debugging enabled (and cephx authentication
di
11 matches
Mail list logo
