Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
docker-debian-artifacts
Official builds of debuerreotype-generated Debian tarballs for use in Docker
postgres:15-bullseye 2bb008a38e7c 379MB
[1] https://github.com/bitnami/minideb
However, it is sometimes a good idea to benchmark the speed of different images, as sometimes a significant speed loss is possible.
What's different between debian:bullseye-slim and debian:bullsye (assuming you are talking about https://hub.docker.com/_/debian)
let me try to answer/research this question myself to find the answer/go on this journey:
takes me to
non slim: https://github.com/debuerreotype/docker-debian-artifacts/tre...
slim: https://github.com/debuerreotype/docker-debian-artifacts/tre...
https://github.com/debuerreotype/docker-debian-artifacts/blo... versus https://github.com/debuerreotype/docker-debian-artifacts/blo...
two files are identical
so at a quick glance i have no clue what is going into rootfs.tar.xz that makes one slim and one not
go to google:
https://stackoverflow.com/questions/59794891/how-does-debian...
Shameless plug, but I've done the same as the author a couple of years ago, but _have_ used docker. Docker is just chroot on steroids right?
Not sure what the persistent storage requirement is about, but what I do, after installing my tool https://gitlab.com/esbs/package_builder-alpine/
```
Related posts
- Minideb: A small image based on Debian designed for use in containers
- Debian 12 is now the base operating system of Bitnami packages
- Dive: A tool for exploring a Docker image, layer contents and more
- Show HN: depot.ai – easily embed ML / AI models in your Dockerfile
- Gitlab docker port number missing on http clone.