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

• Lean and Mean Docker containers

  16 16,044 8.0 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

• distroless

  47 14,674 9.4 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

• InfluxDB

  www.influxdata.com

  sponsored

  Build time-series-based applications quickly and at scale.. InfluxDB is the Time Series Platform where developers build real-time applications for analytics, IoT and cloud-native services. Easy to start, it is available in the cloud or on-premises.

  

• pkg

  43 22,711 7.6 JavaScript

  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

• Tendis

  1 2,503 8.0 C++

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

  

• SSDB

  3 8,013 0.0 C++

  SSDB - A fast NoSQL database, an alternative to Redis

• KeyDB

  6 6,644 9.1 C++

  A Multithreaded Fork of Redis

  

• dynomite

  2 4,028 0.0 C

  A generic dynamo implementation for different k-v storage engines

  

• SonarQube

  www.sonarqube.org

  sponsored

  Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.

  

• tidis

  1 1,413 2.0 Go

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

• anna

  2 625 0.0 C++

  A low-latency, cloud-native KVS

  

• ledisdb

  1 3,932 0.0 Go

  A high performance NoSQL Database Server powered by Go

  

• codis

  1 12,752 0.0 Go

  Proxy based Redis cluster solution supporting pipeline and scaling dynamically

  

• xcodis

  1 185 10.0 Go

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

  

• minideb

  1 1,754 5.8 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/

• containers

  4 896 10.0 Shell

  Bitnami container images

  

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

• SaaSHub

  www.saashub.com

  sponsored

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

  

Suggest a related project