codervinod

I have taken care of welcome banner. Thanks for pointing this out.

  docker run rapidfort/redis
  redis 01:21:19.08
  redis 01:21:19.08 Welcome to the RapidFort optimized, hardened image for Bitnami redis container
  redis 01:21:19.08 Subscribe to project updates by watching https://github.com/rapidfort/community-images
  redis 01:21:19.09 Submit issues and feature requests at https://github.com/rapidfort/community-images/issues/new/choose

It was a genuine mess between me and my friend. He used my account and then switched our accounts. Anyway I understand how it reflects from community point of view. Please accept my sincere apologies in the past post.

RapidFort system, which I am using in the open source community images, allows the user to select files and integrate them into Ci/CD manually. The community images project on GitHub uses Github actions Ci/Cd to achieve the same manual curation.

Missing licenses was a bug in my scripts. I have updated the container images to include all licenses. Thanks for pointing this out.

I have also included metadata in the container. This will allow any scanner to generate the scan report from any tool.

I have also added links to the scan report on the docker hub, so it's easy to see what all CVEs still exist in the docker image. There is no intention to mislead anyone in the community.

I have updated the title to remove confusion. Thanks for calling it out. There was no intention to mislead the community.

It was my first time posting article and my real friend put those comments. I realized it was bad to ask my “real” friends to read the article.

Regarding support, our open source project has issues page, I welcome community to add issues and we will prioritize.

Thanks for pointing licensing issue. I will fix it, this is open source and I am happy to accept and contributions.

Docker slim would help in limited ways. EBF filtering fails at scale and has I here t limitations.

We deleted files from a pre-built container and not Dockerfile.

I would like to understand what’s misleading. You could download the container and compare sizes and binary with source container.

Docker slim tries to solve the same problem with a very different technology. EBF packet filtering doesn’t work for many cases and hence results are sub optimal.

My account was new at that time and HN didn’t allow me to post the article and hence asked my friend. But obviously someone from community flagged. I am happy that community is active but it was a genuine mistake on my end.

Obviously not. There are better ways for spammers to spend their time , rather than writing articles on redis and containers