How to use environment variables to make a containerized Quarkus application more flexible

When you run a containerized application on a container orchestration platform like Kubernetes, Open Shift or with a serverless framework like Knative or Code Engine or on other platforms, it is helpful to pass endpoints to other applications to the containerized application by using environment variables. When the container will be restarted, these variables can be provided to the container and no adjustment in the source code is necessary. You can use configmaps or in Code Engine simple the environment variable itself.

Build a Docker image, push it to Docker hub and clean up local disk space

This blog post does contain the tasks to create a Docker image and upload the image to dockerhub and clean up the image and container on the local machine. Upload the image 1. Create a local Docker image using docker build Dockerhub account name: tsuedbroeckerDockerhub repository name: cns-workshop-toolsTag: v4Docker image name with tag: tsuedbroecker/cns-workshop-tools:v4 docker … Continue reading Build a Docker image, push it to Docker hub and clean up local disk space

Run a PostgreSQL container as a non-root user in OpenShift

In this blog post I want to point out a simple topic: How to run a simple PostgreSQL Docker image as a non-productive container in OpenShift? As you maybe know, OpenShift doesn't allow by default to run container images as root. The image below shows the result of the simply deployed postgreSQL image from dockerhub. It's possible … Continue reading Run a PostgreSQL container as a non-root user in OpenShift