On Tue, Nov 29, 2016 at 10:21 AM, Alban Crequy via iovisor-dev
<[email protected]> wrote:
> Hi,
>
> I think that's a good idea to make it easier to try bcc.
>
> There is this Docker image but I don't know who is managing it:
> https://github.com/zlim/bcc-docker
> https://hub.docker.com/r/zlim/bcc/

Hi Zi,

looks like your docker repo is getting popular :)
If you're planning to maintain it, do you mind sending
a pull-req into iovisor repo, so it's better exposed to the community?

Thanks!

> I was able to run an application using bcc in a Docker container with
> the following privilege flags & volumes (to take the kernel headers
> from the host):
>
> docker run --privileged -d --name=appname --net=host --pid=host \
>               -v /usr/src:/usr/src \
>               -v /lib/modules:/lib/modules \
>               -v /sys/kernel/debug:/sys/kernel/debug \
>               myimagename
>
> The Dockerfile had this content:
>
> FROM ubuntu:yakkety
> RUN echo "deb [trusted=yes] http://52.8.15.63/apt/xenial
> xenial-nightly main" > /etc/apt/sources.list.d/iovisor.list
> RUN apt-get update && \
>         apt-get install -y libelf1 bcc-tools libbcc
>
> To make it a smaller Docker image, I wanted to use Alpine Linux
> instead of Ubuntu but this is currently blocked by this issues:
> https://bugs.alpinelinux.org/issues/6426
> https://bugs.alpinelinux.org/issues/3610
>
> Cheers,
> Alban
>
> On Tue, Nov 29, 2016 at 9:08 AM, 张维(贤维) via iovisor-dev
> <[email protected]> wrote:
>> Hi guys,
>>
>> As we known, to run iovisor require complex build environment, like clang,
>> llvm, python, lua. iovisor and bcc is quite useful for Linux users, but the
>> build environment scared many people to take a try. :)
>>
>> Can we build all these things in one docker image?  I didn't see any docker
>> related install instruction in
>> https://github.com/iovisor/bcc/blob/master/INSTALL.md.
>> User can just pull the iovisor/bcc docker image from dockehub, and run it on
>> local machine, no llvm and clang download, no python and lua download,
>> without affects host. We can call this kind of container as "Super
>> Privileged Containers", according below link. Redhat already tried this on
>> Systemtap.
>>
>> http://rhelblog.redhat.com/2015/11/10/architecting-containers-part-3-how-the-user-space-affects-your-application/
>>
>> Best Regards.
>>
>>
>>
> _______________________________________________
> iovisor-dev mailing list
> [email protected]
> https://lists.iovisor.org/mailman/listinfo/iovisor-dev
_______________________________________________
iovisor-dev mailing list
[email protected]
https://lists.iovisor.org/mailman/listinfo/iovisor-dev

Reply via email to