Docker image layers vernacular – referencing layer order

How do I properly convey a layer is “later” than another layer.

Consider the following Dockerfile:

  • How to deploy docker file on other server
  • Spring Properties from Docker Environment Variables
  • Connecting to rabbitmq docker container from service in another container
  • What are the differences between Kubernetes Pods and Docker Compose(s) (Composures?)
  • Tomee and Postgres communication with Docker
  • How can I filter on Windows-based or Linux-based containers within Docker Hub?
  • FROM ubuntu:15.10
    COPY . /app
    RUN make /app
    CMD python /app/app.py
    

    This Dockerfile contains four commands, each of which creates a layer.

    How do I describe the RUN layer is later than the COPY layer? Context being, later layers that install patches may mitigate vulnerabilities that are introduced in earlier layers.

    In Code

    In code, the CMD layer is the bottom layer. Hence, in code, the lower a layer is, the later it is.

    Docker overview docs

    There is only a reference to a “final” layer.

    About images, containers, and storage drivers | Docker Documentation,

    Docker references layers that supersede other layers in the following ways:

    • last
    • on top
    • before

    Docker image shows later images as “higher”

    Docker image shows later images as "higher"

  • Why does apache2 does not remove pid file on reboot on docker image
  • AWS EB Deploy shows missing Dockerrun.aws.json after deploying
  • Docker Machine vs Docker run
  • Chef-Client fails to get the ruby gem during chef provisioning
  • Cannot update openssl to 1.0.2 on ubuntu docker image
  • Windows container can't ping Ubuntu container in Swarm
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.