IoT and Edge Computing with Podman

The best sources for the Internet of Things (IoT) and Edge Computing propose different requirements and container-based applications than classic server and cloud environments. The Development Team hinted at the container tool Podman, since 2018 as an alternative to Docker, how these trends can be and a valuable functional implementation that enables the deployment of containers in edge computing.

Display

Podman is all about security and next-generation integration into modern Linux systems. Before all traditional Fork-Exec architects of Podman take the Einsatz of containers into new territory. We have used the tool for equipping Kubernetes workloads, soft drinks and Entwickler Cloud-native applications and comfortably on your local workstation programs and equip, or a Zugriff on a Kubernetes cluster has a müssen. Because Podman has found its sources – Kubernetes workloads are available on Raspberry-Pi systems –, it is the bridge that handles traditional manual work of system administration and the modern Cloud-Native world.

Kubernetes and Podman: a perfect team

Modern Kubernetes distribution with Red Hat OpenShift installation and the deployment of a Kubernetes cluster is one of the greatest possibilities that the Entwickeln Cloud-native application often offers in the world. A Kubernetes cluster usually works with the mind of the mind with the most important hardware settings. A number of local and local developers work on the desktop of a working project, with a minikube version, a number of versions of Kubernet and which appear on hervömmliche workstations.

Podman can still write an article and characterize the light use of Kubernetes workloads in the area of ​​IoT and Edge Computing, small resources. There are cloud-native applications on the Raspberry Pi and comparable systems that no longer work, but also do not work. Ganz ohne Kubernetes is nothing more. Within the scope, the machines can be used longer, with answers that can be executed on the container platform. All Podman features are implemented in a support matrix in the Podman documentation.

Podman in the entry

As an example, a containerized application for Kubernetes should serve as a guestbook (see Listing 1). To receive the guestbook in Listing 1, a container is required: a Redis container for the database and a second container for the web frontend, which is placed on port 8080.

apiVersion: v1
kind: Pod
metadata:
  name: guestbook
spec:
  containers:
  - name: backend
image: "docker.io/redis:6"
ports:
- containerPort: 6379
  - name: frontend
image: gcr.io/google_samples/gb-frontend:v6
privileged: true
ports:
- containerPort: 80
  hostPort: 8080
env:
- name: GET_HOSTS_FROM
  value: "env"
- name: REDIS_SLAVE_SERVICE_HOST
  value: "guestbook-backend"

Entry 1: Guestbook

The YAML date is no longer required podman kube play ausführen. An easy access to the two containers in one pod – plus an infrastructure container (see Listing 2).

$ podman kube play guestbook.yaml
Pod:
4d9511ab6f087469cd841885cdba5fd3f36256774a3717f603e26e824acd12e2
Containers:
27649cdbb7627e694359fcd2dc2b6f4659063803610ffa5331373aa29d9b6420
14590a970defcfe70a19eb89660855e5df0a9c35f4c6fb39e227b8d0cb36822a

$ podman pod ps
POD ID      NAME     STATUS  CREATED      INFRA ID     # OF CONTAINERS
4d9511ab6f08  guestbook  Running 25 seconds ago  882814e1cd21  3

$ podman container ps
CONTAINER ID  IMAGE                                COMMAND           CREATED     STATUS     PORTS                                     NAMES
882814e1cd21  localhost/podman-pause:4.5.1-1685123928                    39 seconds ago  Up 37 seconds  0.0.0.0:6379->6379/tcp, 0.0.0.0:8080->80/tcp  4d9511ab6f08-infra
27649cdbb762  docker.io/library/redis:6            redis-server      38 seconds ago  Up 37 seconds  0.0.0.0:6379->6379/tcp, 0.0.0.0:8080->80/tcp  guestbook-backend
14590a970def  gcr.io/google_samples/gb-frontend:v6 apache2-foregroun...  37 seconds ago  Up 37 seconds  0.0.0.0:6379->6379/tcp, 0.0.0.0:8080->80/tcp  guestbook-frontend

Advertisement 2: Container for the guest book

The Container and Pod welding are at Bedarf with the Commando podman kube down stop and bleed.

The software development team is consistent with Kubernetes YAML and the results are followed: This is the result of the implementation of cloud-native applications and the software implementation of the Kubernetes -Cluster . Zum others are using Podman to insult standards – and Kubernetes-YAML that is in practice considered the de facto standard for building container-based workloads. The Podman Development Team has developed the Vision, Kubernetes-YAML is now no longer available in the cloud-native application on a cluster that is used, but also under the standard in some cases this can be adjusted: on the small Raspberry Pi on the local workstation on the embedded system in the Industry or satellites.

Podman is primarily intended for Linux, its features are available via Podman Desktop or on Windows and macOS. Version 1.0 of Tools, all of which is based on active integration with Kubernetes, is scheduled to be released in May 2023.