I deleted 78% of my Redis container and it still works

1. Lean and Mean Docker containers

   1 41 21,504 7.4 Go

   Slim(toolkit): Don't change anything in your container image and minify it by up to 30x (and for compiled languages even more) making it secure too! (free and open source)

   

   Maybe this would help in that regard: https://github.com/docker-slim/docker-slim

2. CodeRabbit

   coderabbit.ai featured

   CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.

   

3. distroless

   2 128 20,343 8.9 Starlark

   🥑 Language focused docker images, minus the operating system.

   

   See: Distroless images[0]

   This is one of the huge benefits of recent systems languages like go and rust -- they compile to single binaries so you can use things like scatch[1] containers. You may have to fiddle with gnu libc/musl libc (usually when getaddrinfo is involved/dns etc), but once you're done with it, packaging is so easy.

   Even languages like Node (IMO the most progressive of the scripting languages) have packages like vercel/pkg[2] which produce native binaries.

   BTW if you're considering running redis these days... Check out KeyDB[3], it's impressive. There are a lot of redis alternatives with interesting features these days that I wonder if running vanilla redis is even a good idea anymore (outside of ensuring complete feature-set compatibility).

   [0]: https://github.com/GoogleContainerTools/distroless

   [1]: https://hub.docker.com/_/scratch/

   [2]: https://github.com/vercel/pkg

   [3]: https://docs.keydb.dev

4. pkg

   3 95 24,099 6.3 JavaScript

   Discontinued Package your Node.js project into an executable

   

   See: Distroless images[0]

   This is one of the huge benefits of recent systems languages like go and rust -- they compile to single binaries so you can use things like scatch[1] containers. You may have to fiddle with gnu libc/musl libc (usually when getaddrinfo is involved/dns etc), but once you're done with it, packaging is so easy.

   Even languages like Node (IMO the most progressive of the scripting languages) have packages like vercel/pkg[2] which produce native binaries.

   BTW if you're considering running redis these days... Check out KeyDB[3], it's impressive. There are a lot of redis alternatives with interesting features these days that I wonder if running vanilla redis is even a good idea anymore (outside of ensuring complete feature-set compatibility).

   [0]: https://github.com/GoogleContainerTools/distroless

   [1]: https://hub.docker.com/_/scratch/

   [2]: https://github.com/vercel/pkg

   [3]: https://docs.keydb.dev

5. Tendis

   4 8 3,035 8.3 C++

   Tendis is a high-performance distributed storage system fully compatible with the Redis protocol.

   

6. SSDB

   5 14 8,203 0.0 C++

   SSDB - A fast NoSQL database, an alternative to Redis

   

7. KeyDB

   6 26 11,914 7.6 C++

   A Multithreaded Fork of Redis

   

8. dynomite

   7 3 4,198 0.0 C

   A generic dynamo implementation for different k-v storage engines

   

9. InfluxDB

   influxdata.com featured

   InfluxDB high-performance time series database. Collect, organize, and act on massive volumes of high-resolution data to power real-time intelligent systems.

   

10. tidis

    8 2 1,436 0.0 Go

    Distributed transactional NoSQL database, Redis protocol compatible using tikv as backend

    

11. anna

    9 3 702 0.0 C++

    A low-latency, cloud-native KVS

    

12. ledisdb

    10 7 4,116 0.0 Go

    A high performance NoSQL Database Server powered by Go

    

13. codis

    11 1 13,185 0.0 Go

    Proxy based Redis cluster solution supporting pipeline and scaling dynamically

    

14. xcodis

    12 1 188 10.0 Go

    Yet another redis proxy based on codis(https://github.com/wandoulabs/codis)

    

15. minideb

    13 6 2,156 7.2 Shell

    A small image based on Debian designed for use in containers

    

    as is stated initially, that goes back to how bitnami is building its Docker images, basing on a set of debian packages (minideb) - there's also a shell library/framework embedded that does useful things, but that makes you read more code when you go check how the sausage is made. That minideb is the basis for the higher CVE count compared to scratch or alpine images.

    > it’s a well-kept secret that no one wants to talk about

    the maintainer side most casual docker image users aren't aware of I'd rephrase, but bitnami at least documents the issue

    https://github.com/bitnami/minideb#security

    https://docs.bitnami.com/kubernetes/open-cve-policy/

16. containers

    14 21 3,767 9.9 Shell

    Bitnami container images

    

    redis 12:06:41.46 Submit issues and feature requests at https://github.com/bitnami/containers/issues

17. SaaSHub

    www.saashub.com featured

    SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

    

Suggest a related project