Docker image layers vernacular – referencing layer order

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

Consider the following Dockerfile:

  • Docker + Django + MySQL - End of list of non-natively partitioned tables
  • Get Docker Container Names
  • Editing a running docker container
  • Is it possible to assign a static public ip to a Docker Container?
  • Deploy Docker container using Kubernetes
  • Redirect container remote calls to other host
  • 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"

  • Docker : Could not resolve host: github.com - for go get ./
  • Unable to start jetty container on Docker cloud
  • docker-compose does not see volumes changes in docker-compose.yml
  • What is the correct way to deploy EAR on Weblogic with Docker
  • Best way to transfer data to named volume of Docker
  • Zypper repository authentication (non-interactive)
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.