You got 3 options: The “ARG” solution, the “base” solution, and “file” solution. ARG version_default=v1 FROM alpine:latest as base1 ARG version_default ENV version=$version_default RUN echo ${version} RUN echo ${version_default} FROM alpine:latest as base2 ARG version_default RUN echo ${version_default} another way is to use base container for multiple stages: FROM alpine:latest as base ARG version_default ENV … Read more
You can stop the build at a certain stage and tag them as you want. docker build –target test -t starx/test:latest . docker build –target staging -t starx/staging:latest . docker build –target prod -t starx/prod:latest . This way, you have different images and you can push each image individually.
ok so my solution is using wheel, it lets us compile on first image, create wheel files for all dependencies and install them in the second image, without installing the compilers FROM python:2.7-alpine as base RUN mkdir /svc COPY . /svc WORKDIR /svc RUN apk add –update \ postgresql-dev \ gcc \ musl-dev \ linux-headers … Read more
ARGs only last for the build phase of a single image. For the multistage, renew the ARG by simply stating: ARG DARSHAN_VER after your FROM instructions. cf. https://docs.docker.com/engine/reference/builder/#arg ARG DARSHAN_VER=3.1.6 FROM fedora:29 as build ARG DARSHAN_VER RUN dnf install -y \ gcc \ make \ bzip2 bzip2-devel zlib zlib-devel RUN curl -O “ftp://ftp.mcs.anl.gov/pub/darshan/releases/darshan-${DARSHAN_VER}.tar.gz” \ && … Read more