Containers

The following features, enhancements, and changes related to containers are introduced in this Oracle Linux 10 release.

Podman Released at Version 5.4

Podman is released at version 5.4. Podman component packages include:

  • podman-5.4
  • buildah-1.39
  • crun-1.19
  • skopeo-1.18

You can install any of these packages directly by using the dnf install command. For example, you can run: 

sudo dnf install podman buildah crun skopeo

Buildah Artifact Manifests

buildah manifest subcommands support new options.

buildah manifest add
  • --artifact
  • --artifact-type
  • --artifact-config-type
  • --artifact-layer-type
  • --artifact-exclude-titles
  • --subject
buildah manifest annotate
  • --index
  • --subject
buildah manifest create
  • --annotation

Disable Podman Healthcheck Events

You can disable the logging of Podman healthcheck events.

In the containers.conf configuration file, locate the new healthcheck_events option under the [engine] section, then set it to healthcheck_events=false.

Persistent Changes to Resources

When you run podman update to modify container configurations, those changes are now persistent. This capability applies to SQLite and BoltDB databases.

Default Settings for Podman Version 5.0

Podman version 5.0 now has the following default settings:

  • cgroups v2 is used instead of cgroups v1.
  • The default network for rootless containers is now pasta instead of slirp4netns.

Handling Compatible Volumes

The --compat-volumes option is now available to provide compatibility with older container volumes. You can specify --compat-volumes with the following commands:
  • buildah build
  • podman build
  • podman farm build

podman pod inspect Returns a JSON Array

Running podman pod inspect always returns a JSON array, even if the command inspects only a single pod.

Customizable Healthcheck Output in Podman

You can now customize the storage of healthcheck output for individual containers in Podman, enabling more detailed debugging information to be retained as needed, and controlling healthcheck output storage for specific containers to address concerns around data sensitivity and storage optimization. This enhancement is useful for troubleshooting sporadic healthcheck failures without impacting the live service. This is a significant improvement over the previous limitations, where healthcheck output was restricted to the five most recent runs, with a character limit of 500 per run, and could only be accessed through the podman inspect command.

Container Storage Configuration File Moved

The default containers storage configuration file is moved from /etc/containers/storage.conf to /usr/share/containers/storage.conf.