I have seen some Docker containers in Dockerhub (https://hub.docker.com/u/slitaz/). As I don't see any link to the Dockerfile / the script to generate those images, I experienced my own versions, e.g,
* A base image https://hub.docker.com/r/icymatter/slitaz40-minimal/ (with bash-4.2, glibc-base-2.13, tazpkg-4.9, coreutils-8.12, curl-7.23, openssl-1.0.0g and pacapt-2.3)
* An image with Ruby-187 https://hub.docker.com/r/icymatter/slitaz40-ruby187/ (I have a legacy application that uses such Ruby). This image uses the base image
The results are impressivily small. But there are many things to improve
* 64-bit version would really help to expand the use of Slitaz with Docker
* Security concerns: The packages are not signed / verified, and it's not good for general use
* It's nice if
tazpkg can remove some package and its dependencies (We may need some development packages, like
glibc-dev to build softwares, but then we need to remove them to minimize the size of Docker image)
* A problem with
tazpkg reported here http://forum.slitaz.org/topic/slitaz-4-tazpkg-deletes-files-if-they-are-in-two-packages
I would start new Docker images with the Slitaz-rolling-64bit.
The question is why we need to use Slitaz with Docker? There are many reasons, definitely! Docker image/ container runs on modern hardware, but the base image should be always secure, lightweight and small. Running with Ubuntu or Debian is fine, but the results image are too heavy and contain a lot of useless things.
There is Alpine Linux, which is based on
musl instead of
glibc. But they also have to build
glibc to support some (many?) applications. They have good use, but I also think Slitaz is good, too.
Let's see how far I can go on this. Feel free to comment and share your ideas.
Thanks for your reading.