<\/p>\n\n\n\n
<\/p>\n\n\n\n
<\/h2>\n\n\n\n\n- <\/a><\/li>\n<\/ul>\n\n\n\n
<\/a> <\/a><\/a> You are here <\/a><\/a><\/a><\/p>\n\n\n\n\n- <\/a><\/li>\n<\/ul>\n\n\n\n
<\/h2>\n\n\n\n\n- <\/a><\/li>\n\n\n\n
- <\/a><\/li>\n<\/ul>\n\n\n\n
<\/h2>\n\n\n\n\n- <\/a><\/li>\n\n\n\n
- <\/a><\/li>\n<\/ul>\n\n\n\n
<\/h2>\n\n\n\n\n- <\/a><\/li>\n<\/ul>\n\n\n\n
<\/p>\n\n\n\n
Containerize a Spring Boot application with Podman Desktop<\/h1>\n\n\n\n
October 19, 2023<\/p>\n\n\n\n
Cedric Clyburn<\/a> Related topics: Containers<\/a>Java<\/a>Kubernetes<\/a>Spring Boot<\/a> Related products: Podman Desktop<\/a>Red Hat Enterprise Linux<\/a><\/p>\n\n\n\nShare:<\/h3>\n\n\n\n
<\/a> <\/a><\/a><\/a><\/p>\n\n\n\nSpring<\/a> and Spring Boot<\/a> are developer favorites for building Java<\/a> applications that run in the cloud. Spring is known for being production-ready, complimenting containerization<\/a> very well. According to the State of Spring 2022<\/a> report, Kubernetes<\/a> has become the dominant platform for running Spring apps. So, how can we take a Spring application, containerize it, and run it locally? Let\u2019s explore this by using Podman Desktop, an open-source tool to seamlessly work with containers and Kubernetes from your local environment.<\/p>\n\n\n\nPrerequisites<\/h2>\n\n\n\n\n- Spring Boot Application: For this article, we\u2019ll use the popular Spring PetClinic<\/a> sample application on GitHub (Figure 1). Feel free to also use your own project\u00a0or start from the Spring Initializr<\/a>.<\/li>\n<\/ul>\n\n\n\n
![\"A](\"https:\/\/developers.redhat.com\/sites\/default\/files\/styles\/article_floated\/public\/screen_shot_2023-10-02_at_10.29.31_am.png?itok=5y--7Zly\")
<\/a>Figure 1: The Spring Petclinic repository on Github.<\/figcaption><\/figure>\n\n\n\n\n- Podman Desktop: Let\u2019s use Podman Desktop<\/a>, the powerful GUI-based tool for deploying and managing containers using the Podman container engine<\/a>. Once installed, you\u2019ll be ready to start containerizing your Spring application (Figure 2).<\/li>\n<\/ul>\n\n\n\n
![\"A](\"https:\/\/developers.redhat.com\/sites\/default\/files\/styles\/article_floated\/public\/screenshot_2023-10-02_at_1.20.08_pm.png?itok=MRVyY_em\")
<\/a>Figure 2: The Podman Desktop dashboard.<\/figcaption><\/figure>\n\n\n\nContainerizing the Spring Boot application<\/h2>\n\n\n\n
Let\u2019s get started by cloning the application’s source code if using the PetClinic repository.<\/p>\n\n\n\n
git clone https:\/\/github.com\/spring-projects\/spring-petclinic.git<\/a>\ncd spring-petclinic<\/pre>\n\n\n\nWhile we can use Maven<\/a> to build a jar file and run it, let\u2019s jump straight into creating a Containerfile in the project\u2019s root directory, which will serve as the blueprint for the container image we\u2019ll create later (analogous to Docker\u2019s Dockerfile). You can create the file with the command touch Containerfile<\/code> or simply create it from your IDE. Let\u2019s see what the Containerfile will look like for this sample Spring Boot application:<\/p>\n\n\n\n# Start with a base image that has Java 17 installed.\nFROM eclipse-temurin:17-jdk-jammy\n\n# Set a default directory inside the container to work from.\nWORKDIR \/app\n\n# Copy the special Maven files that help us download dependencies.\nCOPY .mvn\/.mvn\n\n# Copy only essential Maven files required to download dependencies.\nCOPY mvnw pom.xml.\/\n\n# Download all the required project dependencies.\nRUN .\/mvnw dependency:resolve\n\n# Copy our actual project files (code, resources, etc.) into the container.\nCOPY src.\/src\n\n# When the container starts, run the Spring Boot app using Maven.\nCMD [\".\/mvnw\", \"spring-boot:run\"]\n<\/pre>\n\n\n\nLet\u2019s take a deeper look at the components that make up this Containerfile:<\/p>\n\n\n\n
\n- FROM eclipse-temurin:17-jdk-jammy:\n
\n- Purpose: This line sets the foundation for our container.<\/li>\n\n\n\n
- Deep Dive: It tells Podman to use a pre-existing image that already has Java 17 installed. Think of it as choosing a base flavor for a cake before adding more ingredients. We use the eclipse-temurin<\/a> image because it\u2019s a trusted source for Java installations.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- WORKDIR \/app:\n
\n- Purpose: Designates a working space in our container.<\/li>\n\n\n\n
- Deep Dive: Containers have their own file system. Here, we’re telling Podman to set up a folder named ‘app’ and make it the default location for any subsequent operations.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- COPY commands:\n
\n- Purpose: They transfer files from our local system into the container.<\/li>\n\n\n\n
- Deep Dive: The first COPY grabs Maven<\/a>\u2019s configuration, a tool Java developers use to manage app dependencies. The second copies over the main files of our app: the Maven wrapper (mvnw<\/em>) and the project’s details (pom.xml<\/em>).<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- RUN .\/mvnw dependency:resolve:\n
\n- Purpose: Downloads necessary libraries and tools for the app.<\/li>\n\n\n\n
- Deep Dive: This command activates Maven to fetch everything our app needs to run. By doing this in the Containerfile, we ensure the container has everything packaged neatly.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- COPY src.\/src:\n
\n- Purpose: Add our actual application code.<\/li>\n\n\n\n
- Deep Dive: Our app’s logic, features, and resources reside in the src directory. We’re moving it into the container so that when the container runs, it has our complete app.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- CMD [\u00ab.\/mvnw\u00bb, \u00abspring-boot:run\u00bb]:\n
\n- Purpose: Start our application!<\/li>\n\n\n\n
- Deep Dive: This command is the final step. This line tells Podman to run our Spring Boot application using Maven when our container launches.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
This Containerfile is ready to be used with Podman Desktop to create a container image of our Spring Boot application (Figure 3). Before building the image for this application, let’s double check the directory structure and Containerfile in our IDE of choice.<\/p>\n\n\n\n![\"A](\"https:\/\/developers.redhat.com\/sites\/default\/files\/styles\/article_floated\/public\/screen_shot_2023-09-06_at_10.56.17_pm.png?itok=1ijxka0V\")
<\/a>Figure 3: The Containerfile in VSCode.<\/figcaption><\/figure>\n\n\n\nBuilding the container image with Podman Desktop<\/h2>\n\n\n\n
We can now build our container image with Podman Desktop by first heading to the Images<\/strong> section of Podman Desktop and selecting the Build an Image<\/strong> button in the top-right corner (Figure 4).<\/p>\n\n\n\n![\"A](\"https:\/\/developers.redhat.com\/sites\/default\/files\/styles\/article_floated\/public\/screen_shot_2023-08-30_at_5.21.57_pm.png?itok=VwBkcN51\")
<\/a>Figure 4: The Podman Desktop Build Image is highlighted.<\/figcaption><\/figure>\n\n\n\nThis will open a menu where you can select the path to our previously created Containerfile, which should be in the root directory of the spring-petclinic <\/em>folder. With the Containerfile selected, we can also give our container image a name, for example, petclinic. Now, click on Build<\/strong>, and you\u2019ll see each of the layers of the image being created. You can find this in your local image registry (the Image<\/strong> section in Figure 5).<\/p>\n\n\n\n![\"A](\"https:\/\/developers.redhat.com\/sites\/default\/files\/styles\/article_floated\/public\/screen_shot_2023-08-30_at_5.24.54_pm.png?itok=2MFfCeig\")
<\/a>Figure 5: The Podman Desktop Build Image menu.<\/figcaption><\/figure>\n\n\n\nRunning the containerized application<\/h2>\n\n\n\n
Fantastic! Let\u2019s return to the Images<\/strong> section to see the containerized Spring Boot application, now built and tagged as an image, as well as the eclipse-temurin base image that was downloaded to build our petclinic image. We can easily run this image as a container on our system using the Run<\/strong> icon to the right of our container image (Figure 6).<\/p>\n\n\n\n![\"A](\"https:\/\/developers.redhat.com\/sites\/default\/files\/styles\/article_floated\/public\/screen_shot_2023-08-30_at_5.49.14_pm.png?itok=olz50ECl\")
<\/a>Figure 6: The Podman Desktop showing where to run the container.<\/figcaption><\/figure>\n\n\n\nUnder Port Mapping<\/strong>, make sure to assign port 8080 of the container to port 8080 of the host. Feel free to leave all other settings as default. Click Start Container<\/strong> to launch the containerized instance of your Spring Boot application (Figure 7).<\/p>\n\n\n\n![\"A](\"https:\/\/developers.redhat.com\/sites\/default\/files\/styles\/article_floated\/public\/screen_shot_2023-08-30_at_5.50.38_pm.png?itok=1Q6I4Lv6\")
<\/a>Figure 7: Click the start container button in the Podman Desktop menu.<\/figcaption><\/figure>\n\n\n\nNow, with the container up and running, let\u2019s open the container\u2019s URL in the browser using the handy open browser button within the Podman Desktop user interface (Figure 8).<\/p>\n\n\n\n![\"A](\"https:\/\/developers.redhat.com\/sites\/default\/files\/styles\/article_floated\/public\/screen_shot_2023-08-30_at_5.55.04_pm.png?itok=Z1wRLoLe\")
<\/a>Figure 8: The Podman Desktop highlighting the open browser button.<\/figcaption><\/figure>\n\n\n\nPerfect, looks like our Spring Boot application is running, thanks to the startup command in our Containerfile, as well as the port mapping we configured in Podman Desktop (Figure 9).<\/p>\n\n\n\n![\"A](\"https:\/\/developers.redhat.com\/sites\/default\/files\/styles\/article_floated\/public\/screen_shot_2023-09-05_at_4.17.20_pm.png?itok=idFiYBBg\")
<\/a>Figure 9: The Spring Boot application is running in Chrome.<\/figcaption><\/figure>\n\n\n\nNow we can see this PetClinic application running in our browser, but that\u2019s not all. For more features that may involve bringing out the terminal, we can now use Podman Desktop instead (Figure 10). This may include, SSH\u2019ing into a container for debugging and modifying settings, maybe viewing the logs of a container, or inspecting environment variables. This can all be done under the Container Details<\/strong> section that opens automatically after starting the container.<\/p>\n\n\n\n![\"A](\"https:\/\/developers.redhat.com\/sites\/default\/files\/styles\/article_floated\/public\/okay.png?itok=9V3ZZ_K0\")
<\/a>Figure 10: The Podman Desktop terminal.<\/figcaption><\/figure>\n\n\n\nWrapping up<\/h2>\n\n\n\n
We have gone from local Spring Boot code to containerizing the application and running it with Podman Desktop<\/a>! Now, as a container, we can share this application across environments using registries like Quay.io<\/a> and Docker Hub<\/a> and deploy it using Kubernetes<\/a> and OpenShift<\/a> to a variety of different cloud providers.Last updated: January 15, 2025<\/em><\/p>\n\n\n\nRelated Posts<\/h2>\n\n\n\n\n- Deploying a Spring Boot App with MySQL on OpenShift<\/a><\/li>\n\n\n\n
- Configuring Spring Boot Application on Kubernetes<\/a><\/li>\n\n\n\n
- Deploy and test Kubernetes containers using Podman Desktop<\/a><\/li>\n\n\n\n
- What is Podman Desktop? A developer’s introduction<\/a><\/li>\n<\/ul>\n\n\n\n
Recent Posts<\/h2>\n\n\n\n\n- Multicluster authentication with Ansible Automation Platform<\/a><\/li>\n\n\n\n
- Verify Cosign bring-your-own PKI signature on OpenShift<\/a><\/li>\n\n\n\n
- What’s new in network observability 1.9<\/a><\/li>\n\n\n\n
- How to migrate from Fluentd to Vector in OpenShift 4<\/a><\/li>\n\n\n\n
- How platform engineering accelerates enterprise AI adoption<\/a><\/li>\n<\/ul>\n\n\n\n
What\u2019s up next?<\/h2>\n\n\n\n
Read Podman in Action for easy-to-follow examples to help you learn Podman quickly, including steps to deploy a complete containerized web service. <\/a>LinkedIn<\/a>YouTube<\/a>Twitter<\/a>Facebook<\/a><\/p>\n\n\n\nProducts<\/h3>\n\n\n\n\n- Red Hat Enterprise Linux<\/a><\/li>\n\n\n\n
- Red Hat OpenShift<\/a><\/li>\n\n\n\n
- Red Hat Ansible Automation Platform<\/a><\/li>\n<\/ul>\n\n\n\n
Build<\/h3>\n\n\n\n\n- Developer Sandbox<\/a><\/li>\n\n\n\n
- Developer Tools<\/a><\/li>\n\n\n\n
- Interactive Tutorials<\/a><\/li>\n\n\n\n
- API Catalog<\/a><\/li>\n<\/ul>\n\n\n\n
Quicklinks<\/h3>\n\n\n\n\n- Learning Resources<\/a><\/li>\n\n\n\n
- E-books<\/a><\/li>\n\n\n\n
- Cheat Sheets<\/a><\/li>\n\n\n\n
- Blog<\/a><\/li>\n\n\n\n
- Events<\/a><\/li>\n\n\n\n
- Newsletter<\/a><\/li>\n<\/ul>\n\n\n\n
Communicate<\/h3>\n\n\n\n\n- About us<\/a><\/li>\n\n\n\n
- Contact sales<\/a><\/li>\n\n\n\n
- Find a partner<\/a><\/li>\n\n\n\n
- Report a website issue<\/a><\/li>\n\n\n\n
- Site Status Dashboard<\/a><\/li>\n\n\n\n
- Report a security problem<\/a><\/li>\n<\/ul>\n\n\n\n
RED HAT DEVELOPER<\/h3>\n\n\n\n
Build here. Go anywhere.<\/p>\n\n\n\n
We serve the builders. The problem solvers who create careers with code.<\/p>\n\n\n\n
Join us if you\u2019re a developer, software engineer, web designer, front-end designer, UX designer, computer scientist, architect, tester, product manager, project manager or team lead.<\/p>\n\n\n\n
Sign me up<\/a><\/p>\n\n\n\n\n- About Red Hat<\/a><\/li>\n\n\n\n
- Jobs<\/a><\/li>\n\n\n\n
- Events<\/a><\/li>\n\n\n\n
- Locations<\/a><\/li>\n\n\n\n
- Contact Red Hat<\/a><\/li>\n\n\n\n
- Red Hat Blog<\/a><\/li>\n\n\n\n
- Inclusion at Red Hat<\/a><\/li>\n\n\n\n
- Cool Stuff Store<\/a><\/li>\n\n\n\n
- Red Hat Summit<\/a><\/li>\n<\/ul>\n\n\n\n
\u00a9 2025 Red Hat<\/p>\n\n\n\n
<\/a> <\/a><\/a> You are here <\/a><\/a><\/a><\/p>\n\n\n\n <\/p>\n\n\n\n October 19, 2023<\/p>\n\n\n\n Cedric Clyburn<\/a> Related topics: Containers<\/a>Java<\/a>Kubernetes<\/a>Spring Boot<\/a> Related products: Podman Desktop<\/a>Red Hat Enterprise Linux<\/a><\/p>\n\n\n\n <\/a> <\/a><\/a><\/a><\/p>\n\n\n\n Spring<\/a> and Spring Boot<\/a> are developer favorites for building Java<\/a> applications that run in the cloud. Spring is known for being production-ready, complimenting containerization<\/a> very well. According to the State of Spring 2022<\/a> report, Kubernetes<\/a> has become the dominant platform for running Spring apps. So, how can we take a Spring application, containerize it, and run it locally? Let\u2019s explore this by using Podman Desktop, an open-source tool to seamlessly work with containers and Kubernetes from your local environment.<\/p>\n\n\n\n Let\u2019s get started by cloning the application’s source code if using the PetClinic repository.<\/p>\n\n\n\n While we can use Maven<\/a> to build a jar file and run it, let\u2019s jump straight into creating a Containerfile in the project\u2019s root directory, which will serve as the blueprint for the container image we\u2019ll create later (analogous to Docker\u2019s Dockerfile). You can create the file with the command Let\u2019s take a deeper look at the components that make up this Containerfile:<\/p>\n\n\n\n This Containerfile is ready to be used with Podman Desktop to create a container image of our Spring Boot application (Figure 3). Before building the image for this application, let’s double check the directory structure and Containerfile in our IDE of choice.<\/p>\n\n\n\n We can now build our container image with Podman Desktop by first heading to the Images<\/strong> section of Podman Desktop and selecting the Build an Image<\/strong> button in the top-right corner (Figure 4).<\/p>\n\n\n\n This will open a menu where you can select the path to our previously created Containerfile, which should be in the root directory of the spring-petclinic <\/em>folder. With the Containerfile selected, we can also give our container image a name, for example, petclinic. Now, click on Build<\/strong>, and you\u2019ll see each of the layers of the image being created. You can find this in your local image registry (the Image<\/strong> section in Figure 5).<\/p>\n\n\n\n Fantastic! Let\u2019s return to the Images<\/strong> section to see the containerized Spring Boot application, now built and tagged as an image, as well as the eclipse-temurin base image that was downloaded to build our petclinic image. We can easily run this image as a container on our system using the Run<\/strong> icon to the right of our container image (Figure 6).<\/p>\n\n\n\n Under Port Mapping<\/strong>, make sure to assign port 8080 of the container to port 8080 of the host. Feel free to leave all other settings as default. Click Start Container<\/strong> to launch the containerized instance of your Spring Boot application (Figure 7).<\/p>\n\n\n\n Now, with the container up and running, let\u2019s open the container\u2019s URL in the browser using the handy open browser button within the Podman Desktop user interface (Figure 8).<\/p>\n\n\n\n Perfect, looks like our Spring Boot application is running, thanks to the startup command in our Containerfile, as well as the port mapping we configured in Podman Desktop (Figure 9).<\/p>\n\n\n\n Now we can see this PetClinic application running in our browser, but that\u2019s not all. For more features that may involve bringing out the terminal, we can now use Podman Desktop instead (Figure 10). This may include, SSH\u2019ing into a container for debugging and modifying settings, maybe viewing the logs of a container, or inspecting environment variables. This can all be done under the Container Details<\/strong> section that opens automatically after starting the container.<\/p>\n\n\n\n We have gone from local Spring Boot code to containerizing the application and running it with Podman Desktop<\/a>! Now, as a container, we can share this application across environments using registries like Quay.io<\/a> and Docker Hub<\/a> and deploy it using Kubernetes<\/a> and OpenShift<\/a> to a variety of different cloud providers.Last updated: January 15, 2025<\/em><\/p>\n\n\n\n Read Podman in Action for easy-to-follow examples to help you learn Podman quickly, including steps to deploy a complete containerized web service. <\/a>LinkedIn<\/a>YouTube<\/a>Twitter<\/a>Facebook<\/a><\/p>\n\n\n\n Build here. Go anywhere.<\/p>\n\n\n\n We serve the builders. The problem solvers who create careers with code.<\/p>\n\n\n\n Join us if you\u2019re a developer, software engineer, web designer, front-end designer, UX designer, computer scientist, architect, tester, product manager, project manager or team lead.<\/p>\n\n\n\n Sign me up<\/a><\/p>\n\n\n\n \u00a9 2025 Red Hat<\/p>\n\n\n\n\n
<\/h2>\n\n\n\n
\n
<\/h2>\n\n\n\n
\n
<\/h2>\n\n\n\n
\n
Containerize a Spring Boot application with Podman Desktop<\/h1>\n\n\n\n
Share:<\/h3>\n\n\n\n
Prerequisites<\/h2>\n\n\n\n
\n
<\/a>\n
<\/a>Containerizing the Spring Boot application<\/h2>\n\n\n\n
git clone https:\/\/github.com\/spring-projects\/spring-petclinic.git<\/a>\ncd spring-petclinic<\/pre>\n\n\n\n
touch Containerfile<\/code> or simply create it from your IDE. Let\u2019s see what the Containerfile will look like for this sample Spring Boot application:<\/p>\n\n\n\n# Start with a base image that has Java 17 installed.\nFROM eclipse-temurin:17-jdk-jammy\n\n# Set a default directory inside the container to work from.\nWORKDIR \/app\n\n# Copy the special Maven files that help us download dependencies.\nCOPY .mvn\/.mvn\n\n# Copy only essential Maven files required to download dependencies.\nCOPY mvnw pom.xml.\/\n\n# Download all the required project dependencies.\nRUN .\/mvnw dependency:resolve\n\n# Copy our actual project files (code, resources, etc.) into the container.\nCOPY src.\/src\n\n# When the container starts, run the Spring Boot app using Maven.\nCMD [\".\/mvnw\", \"spring-boot:run\"]\n<\/pre>\n\n\n\n
\n
\n
\n
\n
\n
\n
\n
<\/a>Building the container image with Podman Desktop<\/h2>\n\n\n\n
<\/a><\/a>Running the containerized application<\/h2>\n\n\n\n
<\/a><\/a><\/a><\/a><\/a>Wrapping up<\/h2>\n\n\n\n
Related Posts<\/h2>\n\n\n\n
\n
Recent Posts<\/h2>\n\n\n\n
\n
What\u2019s up next?<\/h2>\n\n\n\n
Products<\/h3>\n\n\n\n
\n
Build<\/h3>\n\n\n\n
\n
Quicklinks<\/h3>\n\n\n\n
\n
Communicate<\/h3>\n\n\n\n
\n
RED HAT DEVELOPER<\/h3>\n\n\n\n
\n