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:
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.
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.
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.
To see the changes I made to the eventuate-examples-docker-images
project, take a look at this Github commit.
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.
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.
Chris teaches comprehensive workshops for architects and developers that will enable 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.
Learn moreChris offers numerous other resources for learning the microservice architecture.
Want to see an example? Check out Chris Richardson's example applications. See code
Got a specific microservice architecture-related question? For example:
Consider signing up for a two hour, highly focussed, consulting session.
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 MECNPWNR to sign up for $120 (valid until May 16th, 2023). There are deeper discounts for buying multiple seats.
Take a look at my Manning LiveProject that teaches you how to develop a service template and microservice chassis.
Engage Chris to create a microservices adoption roadmap and help you define your microservice architecture,
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.
Engage Chris to conduct an architectural assessment.
Note: tagging is work-in-process
anti-patterns · application api · application architecture · architecting · architecture documentation · assemblage · beer · containers · dark energy and dark matter · deployment · design-time coupling · development · devops · docker · eventuate platform · glossary · hexagonal architecture · implementing commands · implementing queries · inter-service communication · kubernetes · 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 · tacos · team topologies · transaction management · transactional messaging