Updated Docker images location

[ader1990]

Hello,

The images published here https://github.com/iovisor/bcc/pkgs/container/bcc seem to be build images, as I cannot find the installed bcc tools.

Is there a place where the equivalent of https://quay.io/repository/iovisor/bcc images (already the latest is 2 years old) are present or maybe the build images from ghcr.io already have the built packages at another path?

Thank you.

[ader1990]

Also, the quickstart document points to https://hub.docker.com/r/zlim/bcc, which is 5 years old - https://github.com/iovisor/bcc/blob/master/QUICKSTART.md#quick-start-guide

[Wh1isper]

Yes, I built my own bcc image based on ubuntu2204, which currently supports linux/amd64 and linux/arm64: https://hub.docker.com/repository/docker/dataucon/ubuntu-bcc/

Dockerfile: https://github.com/hitsz-ids/dataucon/blob/main/docker/Dockerfile.bcc Github Actions: https://github.com/hitsz-ids/dataucon/actions/workflows/build-bcc.yml Tutorial for running bcc in docker(actually my project based on bcc, you can replace the image and ignore port forward...): https://github.com/hitsz-ids/duetector/blob/main/docs/how-to/run-with-docker.md

FYI

[ader1990]

@Wh1isper that is great news.

One small suggestion --> I have created a new PR here to fix the iovisor/bcc Dockerfile builds: https://github.com/iovisor/bcc/pull/4822

The images here https://hub.docker.com/r/dataucon/ubuntu-bcc are 3.48 GB in size decompressed (1GB compressed) because the images are traling the build env with them.

With my above PR, the image size decompressed is only 585 MB in size.

Would you consider creating the images using the PR from upstream if it gets merged? Or I can make a PR to your repo directly.

Thank you, Adrian Vladu

[Wh1isper]

@ader1990 No problem, it's great if there is an available distribution package(or image) upstream I can just use it. I will most likely create a new image for installing and delivering the application using the distributed package.

Additiona, if I understand correctly, the non-removable weight is generally the LLVM. Maybe I could also try to reduce the size of the package using a two-step build.

Thanks for your work!

[ader1990]

@ader1990 No problem, it's great if there is an available distribution package upstream I can just use it. I will most likely create a new image for installing and delivering the application using the distributed package.

Additiona, if I understand correctly, the non-removable weight is generally the LLVM. Maybe I could also try to reduce the size of the package using a two-step build.

Thanks for your work!

I have not seen an updated upstream for Debian/Ubuntu, that s why I wanted to at least fix the deb package build and the Docker build first. Only the maintainers from this project have access to the Debian/Ubuntu repos.

Thanks!