Suppose that there are a series of build and push commands that we need to do inorder to build a docker image and push it to artifact registry for example, Makefile can help us run a series of commands in serial order in command line which helps us kind of semi automate this process.
For example:
FROM python:3.10
LABEL maintainer=Dinesh
ENV PYTHONBUFFERED 1
WORKDIR /app/
RUN mkdir -p ./src
ADD . /src/
RUN pip install keyring keyrings.google-artifactregistry-auth
RUN --mount=type=secret,id=creds,target=/root/.config/gcloud/application_default_credentials.json \
pip install --no-cache-dir -r requirements.txt
RUN chmod +x ./src/startup_script.sh
ENTRYPOINT ["./src/startup_script.sh"]
In any project, we first write a Dockerfile, build this file, push the docker image to artifact registry, and then use Kubernetes manifest to pull and install the docker image.
I will give an example of building and pushing the Docker image to Artifact registry
GCR_URL=asia-docker.pkg.dev/gcp-project-name
REGISTRY_URL=asia-northeast1-python.pkg.dev
BASE_IMAGE_NAME=services/run_training_job
BASE_IMAGE_VERSION=base-0.1
IMAGE_NAME=services/run_training_job
STAGING_IMAGE_TAG=staging-0.1
PRODUCTION_IMAGE_TAG=production-0.1
IMAGE_TAG=${PRODUCTION_IMAGE_TAG}
ENV=prod
build_and_push:
docker-build docker-push
docker-build:
docker build -f Dockerfile -t ${BASE_IMAGE_NAME}:${IMAGE_TAG} --no-cache \
--build-arg BASE_IMAGE=${GCR_URL}/${BASE_IMAGE_NAME}:${BASE_IMAGE_VERSION} \
.
docker-push:
docker tag ${IMAGE_NAME}:${IMAGE_TAG} ${GCR_URL}/${IMAGE_NAME}:${IMAGE_TAG}
gcloud auth login
docker push ${GCR_URL}/${IMAGE_NAME}:${IMAGE_TAG}
If we run the following command, it will take care of building and push the image to artifact registry
make build_and_push
build_and_push command is actually executing two other steps, first docker-build and the docker-push