installation-of-podman-to-run-docker-container-part-1

Our lab guys at Opvizor always try to find the new and upcoming DevOps tools that our customers might use in the future – or maybe us internally.

This time we thought its time to try the installation of Podman and Buildah, a toolset for run and manage docker and kubernetes container.

We typically use Debian, Ubuntu or Photon OS as our operating system base, but this time we wanted to give Fedora 29 a try.

Let’s get into the details and install Fedora and Podman.

What is Podman?

Before we dig into the installation of Podman, lets get into some details what Podman is all about.

Simply put: `alias docker=podman` is stated on the website and for most of the command line parameters that’s exactly true. But Podman is a more secure way to run container.

Podman uses a traditional fork/exec model for the container, so the container process is an offspring of the Podman process, while Docker uses a client/server model. The docker command is executed by the Docker client tool, and it communicates with the Docker daemon via client/server operations. The Docker daemon creates the container and handles communications of stdin/stdout back to the Docker client tool.

The default loginuid of processes (before their loginuid is set) is 4294967295. Since the container is an offspring of the Docker daemon and the Docker daemon is a child of the init system, we see that systemd, Docker daemon, and the container processes all have the same loginuid, 4294967295, which audit refers to as the unset audit UID.

Podman is a container runtime providing a very similar features as Docker. And as already hinted, it doesn’t require any daemon to run on your system, and it can also run without root privileges. 

There is a nice article covering a lot of the differences between Podman and docker.

https://developers.redhat.com/blog/2019/02/21/podman-and-buildah-for-docker-users/

Fedora 29 installation

The Fedora installation is quite straightforward, so nothing special to show. Just make sure that you either create a decent sized second disk or make sure your first disk is large enough to store some container images without filling up. I go for 32GB as a demo box starter.

Fedora configure fix IP

Unfortunately nearly all linux distributions have a different idea of network configuration. Therefore, let’s add the procedure here.

Start with a ifconfig to see the used network adapter, i. e. ens192

vi /etc/sysconfig/network-scripts/ifcfg-ens192TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=ens192 UUID=54d4f9f9-fb85-317c-bc44-xxxxxxxxxxxx ONBOOT=yes AUTOCONNECT_PRIORITY=-999 DEVICE=ens192

and change it to your static configuration, i. e. 192.168.0.200

TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=ens192 UUID=54d4f9f9-fb85-317c-bc44-fxxxxxxxxxxxx ONBOOT=yes AUTOCONNECT_PRIORITY=-999 DEVICE=ens192 IPADDR=192.168.0.230 PREFIX=24 GATEWAY=192.168.0.1 DNS1=9.9.9.9

sudo reboot afterwards to get the new configuration live.

Fedora Update and installation of Podman

First thing to do is of course the update of existing packages and the installation of new packages required to run Podman.

sudo dnf update sudo dnf install -y podman

Installation of Podman

Installation finished successfully for Fedora. When using a different distribution like Ubuntu, Debian or whatever, please check the installation readme of Podman.

Podman commands

When you’re used to the docker command, podman is amazingly simple to learn – you can just use the same parameters.

podman ps # show all running container

podman ps -a # show all container

podman images # show all container images

The last command might make you think, if you already have docker and docker container images installed – nothing shows up. Reason is, that podman uses a different location to store the container images.

Run a simple "Hello World" with a one-time container

podman run –rm -it fedora:28 echo "Hello world!"

Building a new container works exactly as docker.

cat Dockerfile FROM fedora:28 RUN dnf -y install cowsaypodman build . -t hello-worldpodman run –rm -it hello-world cowsay "Hello!"

Next post we’re digging into Buildah and more Podman commands.

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.