Publishing multi-architecture base images for services

The eventuate-examples-docker-images project publishes Docker base images for the services, such as those in the Eventuate Tram Customers and Orders example application. A service base image has a health check that pings the service’s health check endpoint. It also ensures that a service’s Docker image uses the correct Java version with some suitable heap settings. This post describes how I changed the project to publish a multi-architecture base image for Spring services. I first describe the changes to the Dockerfile. After that, I describe the changes to the CircleCI pipeline.

The other articles in this series are:

Changing the Dockerfile to use a multi-architecture base image

This project builds and publishes separate service base images for Spring Boot, Micronaut, and Quarkus-based services. That’s because the Docker image’s health check must ping a framework-specific health check endpoint. I decided to first publish a multi-architecture Spring Boot base image.

I changed its Dockerfile to use multi-architecture base image. Originally, its Dockerfile used an openjdk:8 base image. I changed it to use the multi-architecture amazoncorretto:17.0.1-al2 base image:

FROM amazoncorretto:17.0.1-al2
HEALTHCHECK --start-period=30s --interval=5s CMD curl -f http://localhost:8080/actuator/health || exit 1
CMD java ${JAVA_OPTS:-"-Xmx64m"} -jar ${JAR:-"service.jar"}

Let’s now look at the changes I made to the CircleCI pipeline.

Configuring the CircleCI pipeline to run docker buildx build

This project has a very simple CircleCI pipeline. It consists of a single job that simply builds and publishes the Docker images. There are no tests (oops).

As a result, I only needed to make a couple of simple changes to the pipeline. First, I explicitly specified an up to date remote Docker:

- setup_remote_docker:
    version: 20.10.11

Next, I added a job step that runs docker buildx build to build and publish the multi-architecture base image for Spring services:

- run:
    name: Publish multi-arch artifacts
    command: |
      docker context create tls-env
      docker buildx create tls-env --use
      docker run --privileged --rm tonistiigi/binfmt --install arm64,arm
      ./deploy-multi-arch-artifacts.sh

The deploy-multi-arch-artifacts.sh script runs docker buildx build, which publishes the base image for Spring services to Docker Hub. I also removed the Spring base image from the Docker Compose file so that the single architecture version is no longer built.

Using the base images

Once the project’s CircleCI pipeline was successfully publishing the multi-architecture base image, I changed the Eventuate Tram Customers and Orders example application’s services’ (customer-service, order-service and order-history-service) Dockerfiles to use it. For example:

ARG baseImageVersion
FROM eventuateio/eventuate-examples-docker-images-spring-example-base-image:$baseImageVersion
ARG jarDir=build/libs
COPY $jarDir/customer-service-*.jar service.jar

The example application is now one step closer to running on my MacBook.

Viewing the changes

To see the changes I made to the eventuate-examples-docker-images project, take a look at this Github commit.

Next steps

In the next article, I’ll describe the changes that I made to the eventuate-cdc project so that it publishes a multi-architecture Eventuate CDC service.



Copyright © 2023 Chris Richardson • All rights reserved • Supported by Kong.

About Microservices.io

Microservices.io is brought to you by Chris Richardson. Experienced software architect, author of POJOs in Action, the creator of the original CloudFoundry.com, and the author of Microservices patterns.

Chris helps clients around the world adopt the microservice architecture through consulting engagements, and training workshops.

Learn how to create a service template and microservice chassis

Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.

New virtual bootcamp: Distributed data patterns in a microservice architecture

My virtual bootcamp, distributed data patterns in a microservice architecture, is now open for enrollment!

It covers the key distributed data management patterns including Saga, API Composition, and CQRS.

It consists of video lectures, code labs, and a weekly ask-me-anything video conference repeated in multiple timezones.

The regular price is $395/person but use coupon JUNVCEJE to sign up for $195 (valid until February 1st, 2023). There are deeper discounts for buying multiple seats.

Learn more

Signup for the newsletter


LEARN about microservices

Chris offers numerous resources for learning the microservice architecture.

Training classes

Chris teaches comprehensive workshops, training classes and bootcamps for executives, architects and developers to help your organization use microservices effectively.

Avoid the pitfalls of adopting microservices and learn essential topics, such as service decomposition and design and how to refactor a monolith to microservices.

Delivered in-person and remotely.


Get the book: Microservices Patterns

Read Chris Richardson's book:

Example microservices applications

Want to see an example? Check out Chris Richardson's example applications. See code

BUILD microservices

Ready to start using the microservice architecture?

Consulting services

Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,


The Eventuate platform

Use the Eventuate.io platform to tackle distributed data management challenges in your microservices architecture.

Eventuate is Chris's latest startup. It makes it easy to use the Saga pattern to manage transactions and the CQRS pattern to implement queries.

ASSESS your architecture

Assess your application's microservice architecture and identify what needs to be improved.

Consulting services

Engage Chris to conduct an architectural assessment.



Join the microservices google group

Topics

Note: tagging is work-in-process

anti-patterns   ·  application api   ·  application architecture   ·  architecting   ·  architecture documentation   ·  dark energy and dark matter   ·  deployment   ·  development   ·  devops   ·  docker   ·  implementing commands   ·  implementing queries   ·  inter-service communication   ·  loose coupling   ·  microservice architecture   ·  microservice chassis   ·  microservices adoption   ·  microservicesio updates   ·  multi-architecture docker images   ·  observability   ·  pattern   ·  refactoring to microservices   ·  resilience   ·  sagas   ·  security   ·  service api   ·  service collaboration   ·  service design   ·  service discovery   ·  service granularity   ·  service template   ·  software delivery metrics   ·  success triangle   ·  team topologies   ·  transaction management   ·  transactional messaging

All content


Posts

24 Jul 2017 » Revised data patterns