Openshift: Lab 12 - Build your application from a container image

Turn Your Vehicle Into a Smart Earning Asset

While you’re not driving your car or bike, it can still be working for you. MOTOSHARE helps you earn passive income by connecting your vehicle with trusted renters in your city.

🚗 You set the rental price
🔐 Secure bookings with verified renters
📍 Track your vehicle with GPS integration
💰 Start earning within 48 hours

It’s simple, safe, and rewarding. Your vehicle. Your rules. Your earnings.

In this lesson, you will:

Set up your Developer Sandbox
Set up a cluster
Build the application from a container image

Build the application from a container image

To build your application from a container image, switch to the Developer view in your OpenShift dashboard (Figure 8):

Next, select +Add to display the many options available for adding an application to your cluster (Figure 9).

Figure 3: Select +Add to display the available options.

In our case, we are interested in the Git Repository/Import from Git option. Select Import from Git (Figure 10).

Figure 4: Selecting Import from Git will build an application from your source code.

You will be prompted to enter a URL that points to a Git repo. This is where things get interesting. OpenShift will copy the repo to an internal storage location, inspect it, and attempt to discern the import strategy to build it.

OpenShift will choose one of the following methods to build the application:

Option 1: Using the Builder image for the programming language used (i.e., the s2i option).
Option 2: Using the Dockerfile that is found in the Git repo.
Option 3: Using the DevFile that is found in the Git Repo.

Again, we’re focusing on Option 1 right now: Using the Builder image and the s2i technology. The Builder image is determined by inspecting the source code and may be .NET, JBoss, Perl, or one of several other options.

Here are some URLs of sample code that you can use for their related languages:

Select the Container images option (Figure 11).

Figure 11: Use this option to run an existing container image in OpenShift.

This is the option I use 100% of the time. I like to build and test my images on my PC, then push them to my image registry (quay.io/donschenck). Once I host an image in a registry, it’s very simple to get it into OpenShift.

Just like the other two options, the simplest path is to provide the location of the input—an image in this case (Figure 12), and click Create. Yes, it really is that simple.

Figure 12: Provide the location of the input and click Create.

Rajesh Kumar

I’m a DevOps/SRE/DevSecOps/Cloud Expert passionate about sharing knowledge and experiences. I have worked at Cotocus. I share tech blog at DevOps School, travel stories at Holiday Landmark, stock market tips at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow , and SEO strategies at Wizbrand.

Do you want to learn Quantum Computing?

Please find my social handles as below;

Rajesh Kumar Personal Website
Rajesh Kumar at YOUTUBE
Rajesh Kumar at INSTAGRAM
Rajesh Kumar at X
Rajesh Kumar at FACEBOOK
Rajesh Kumar at LINKEDIN
Rajesh Kumar at WIZBRAND

Certification Courses

DevOpsSchool has introduced a series of professional certification courses designed to enhance your skills and expertise in cutting-edge technologies and methodologies. Whether you are aiming to excel in development, security, or operations, these certifications provide a comprehensive learning experience. Explore the following programs: