What is the point of intermediate CMD layers in Docker images?

This page summarizes the projects mentioned and recommended in the original post on /r/docker

InfluxDB
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Our great sponsors

  • Python-docker

    Docker Official Image packaging for Python (by docker-library)

    • The authors of the python:3.9.17-slim-bullseye image need an OS for python to run on, and chose to implement this by copying from debian:bullseye-slim. Then they layer the steps to install and configure python on top of that base image. They end by overriding the CMD statement to point to python3 instead of bash since you would reasonably expect a python container to run python and not bash. You can see all this in the Dockerfile for python:3.9.17-slim-bullseye.

  • 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.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts