Developing Spring Boot Application using Docker - Part 1

-

Recently I have been stormed by the now old buzz word Docker. I have been reading a lot about Docker for quite some time and found some abundant resources out there on internet. I am planning to add more to the series in my later posts. I will be posing my blogs as and when I am learning and discovering something new in my journey. It's never too late to start something is what I believe. Lets get started.


Prerequisites

Prerequisites for this project.

  1. An IDE of your choice
  2. Java 11
  3. Docker

Section 1: Lets Start from start.spring.io

If you already have a working Spring Boot Application, head to Section 2.
We can build the Spring Boot Project by just visiting the below link.
URL to generate Simple Spring Boot App on start.spting.io
This should get you started with a typical Spring Boot Application





Now lets download and extract the project to workspace. Extract files using

$ unzip -d ~/your/fav/location/ docker-example.zip


or your GUI tool installed on you computer.

Now it is time for adding a simple Hello World Controller. Add new Controller as shown.



To ensure the Controller looks good, run the following command.

$ ./gradlew clean assemble bootRun


If you want to test the endpoint, open a browser and visit, http://localhost:8080/hello.



Now that you have a working application lets containerize it.


Section 2: Adding Docker to Spring Boot Application


Now that we have a simple Spring Boot Application running, it is time to get the Docker files added to the project and have that run.

Before we could add our Dockerfile we need to add the following to our gradle.build file.


This will ensure the generated artifact is given a name that can be used by docker to create the container image.

Create a Dockerfile as follows.


Now that you have a Dockerfile, lets create a docker-compose.yml.

Before heading to create a Container, we will have to generate the artifact to be shipped into the container.

Lets build our artifact using the Gradle command


$ ./gradlew clean assemble



The new packaged jar file should be located inside your project directory/build/libs.

Here is the command to run the docker/compose with –build option.

Starting the application with –build option, will be able to recreate containers every time.

We wanted that feature so that when we make changes to the jar file it is automatically picked.


$ docker-compose up -d --build




Time to see the output from container. Head to your browser and hit http://localhost:8080/hello.

Our Spring Boot App finally runs inside the container. Now, it is time to add stop our container.

To stop our running container run the following:

$ docker-compose down



Recap of what we just did

  • When we ran the Gradle task, we created the Spring Boot jar file that we wanted to deploy inside the container.
  • When we added the Dockerfile, it had the details like what image we need to start with
    • FROM adoptopenjdk:11-jdk: This specifies we need to download the Java 11 Image for building our container/image.
    • EXPOSE 8080: We are exposing port 8080 to be accessed outside the container.
    • ADD build/libs/docker-example.jar /app/: This copies the generated artifact into the container/image.
    • WORKDIR /app: Before running any command, we are changing directory into the working application folder.
    • CMD java -jar docker-example.jar: This runs the Spring Boot application as Java process.
  • When we added docker-compose.yml it had details on how to start the Dockerfile and start the container
    • version: "3": Specify the version of the composer.
    • services.docker-example.build.context: .: This specifies the context for the docker to be executed.
    • services.docker-example.build.dockerfile: Dockerfile: Mention the Docker file that needs to be executed.
    • services.docker-example.ports: - 8080:8080: Exposing the docker port on local computer.

Next Stage

In our next stage we can use our IDE and debug application that is running inside the container.
The code for this blog can be found here: https://github.com/reflexdemon/docker-example/tree/part-1
If you liked the blog, poke me on my Twitter @reflexdemon






















Comments

Post a Comment

Popular posts from this blog

Java SSL/TLS Testing Tool: Cipher Suite

-
Image
Recently I was reading about the TLS/SSL and Ciphers. I was also interested to read about the Ciphers that are provided out of the box with JDK. This looked to me like this is something we take it for granted and do not do our due diligence when talking about the Ciphers. We often times leave those topic to our organization's network and security team. From my experience, it is a topic that all the developers leave it to the Sr. Developers and then the Sr. Developers pass it on to the Management. Guess what? It is not a sweet topic to discussion. To break this kind of symptom, I have choose to make it simple and want everyone to understand the complexity and importance of knowing this. Lets get started Before we wet our hands here is some basic information that you will require to know, Word Meaning Protocol A defined set of rules and regulations that determine how data is transmitted in telecommunications and computer networking SSL
Read more

PWA: Building and publishing a PWA in 15ish minutes using Angular 5 and Service Worker

-
Image
Introduction Here is an express start to your first PWA with service workers and a 100% score from lighthouse. I have taken it as a challenge to be able to present it to you so that you may be able to put your first pwa "hello world" app in 15ish minutes. What is PWA? Progressive web apps (PWAs) take traditional web sites/applications — with all of the advantages the web brings — and add a number of features that give them many of the user experience advantages of native apps. This set of docs tells you all you need to know. - Source: https://developer.mozilla.org/en-US/Apps/Progressive If the above definition sounds interesting, then this is to get you kickstarted with PWA using Angular 5 and inspire you to build more PWAs. End of this post you should be able to build, host and publish a PWA and get motivated to read more about it. Ever since I read about PWAs It has intrested me like crazy. Before, you get excited about PWA, please look into the supported brow
Read more

Yarn and Angular-CLI

-
Background I have been thinking of a faster package management tool ever since I started using NPM (Node Package Manager). Please don’t mistake me having anything against NPM. I still love this package manager and I very much love the rich command-line that it came with. When it was created, it was really the leader and because of this NPM the whole JS world has seen a revolution. NPM surly was the spark to the revolution in the JS (Java Script) world. To make it clear for everyone why we needed a new package manager is because of the following challenges that we had with NPM, 1.      The Nested dependencies that was sometimes going in infinity loops. At times, it was impossible to delete files on the PC as the paths were too nested. 2.      Everything on the world had to depend on only one registry. https://www.npmjs.com/ 3.      Single threaded installation. The installation of the dependencies are single threaded. 4.      You are always expected to be online even i
Read more