v5.3.0
Features
- The
podman kube generateandpodman kube playcommands can now create and run Kubernetes Job YAML (#17011). - The
podman kube generatecommand now includes information on the user namespaces for pods and containers in generated YAML. Thepodman kube playcommand uses this information to duplicate the user namespace configuration when creating new pods based on the YAML. - The
podman kube playcommand now supports Kubernetes volumes of type image (#23775). - The service name of systemd units generated by Quadlet can now be set with the
ServiceNamekey in all supported Quadlet files (#23414). - Quadlets can now disable their implicit dependency on
network-online.targetvia a new key,DefaultDependencies, supported by all Quadlet files (#24193). - Quadlet
.containerand.podfiles now support a new key,AddHost, to add hosts to the container or pod. - The
PublishPortkey in Quadlet.containerand.podfiles can now accept variables in its value (#24081). - Quadlet
.containerfiles now support two new keys,CgroupsModeandStartWithPod, to configure cgroups for the container and whether the container will be started with the pod it is part of (#23664 and #24401). - Quadlet
.containerfiles can now use the network of another container by specifying the.containerfile of the container to share with in theNetworkkey. - Quadlet
.containerfiles can now mount images managed by.imagefiles into the container by using theMount=type=imagekey with a.imagetarget. - Quadlet
.podfiles now support six new keys,DNS,DNSOption,DNSSearch,IP,IP6, andUserNS, to configure DNS, static IPs, and user namespace settings for the pod (#23692). - Quadlet
.imagefiles can now give an image multiple times by specifying theImageTagkey multiple times (#23781). - Quadlets can now be placed in the
/run/containers/systemddirectory as well as existing directories like$HOME/containers/systemdand/etc/containers/systemd/users. - Quadlet now properly handles subdirectories of a unit directory being a symlink (#23755).
- The
podman manifest inspectcommand now includes the manifest's annotations in its output. - The output of the
podman inspectcommand for containers now includes a new field,HostConfig.AutoRemoveImage, which shows whether a container was created with the--rmioption set. - The output of the
podman inspectcommand for containers now includes a new field,Config.ExposedPorts, which includes all exposed ports from the container, improving Docker compatibility. - The output of the
podman inspectcommand for containers now includes a new field,Config.StartupHealthCheck, which shows the container's startup healthcheck configuration. - The output of the
podman inspectcommand for containers now includes a new field inMounts,SubPath, which contains any subpath set for image or named volumes. - The
podman machine listcommand now supports a new option,--all-providers, which lists machines from all supported VM providers, not just the one currently in use. - VMs run by
podman machineon Windows will now provide API access by exposing a Unix socket on the host filesystem which forwards into the VM (#23408). - The
podman buildx pruneandpodman image prunecommands now support a new option,--build-cache, which will also clean the build cache. - The Windows installer has a new radio button to select virtualization provider (WSLv2 or Hyper-V).
- The
--add-hostoption topodman create,podman run, andpodman pod createnow supports specifying multiple hostnames, semicolon-separated (e.g.podman run --add-host test1;test2:192.168.1.1) (#23770). - The
podman runandpodman createcommands now support three new options for configuring healthcheck logging:--health-log-destination(specify where logs are stored),--health-max-log-count(specify how many healthchecks worth of logs are stored), and--health-max-log-size(specify the maximum size of the healthcheck log).
Changes
- Podman now uses the Pasta
--map-guest-addroption by default which is used for thehost.containers.internalentry in/etc/hoststo allow containers to reach the host by default (#19213). - The names of the infra containers of pods created by Quadlet are changed to the pod name suffixed with
-infra(#23665). - The
podman system connection addcommand now respects HTTP path prefixes specified withtcp://URLs. - Proxy environment variables (e.g.
https_proxy) declared incontainers.confno longer escape special characters in their values when used withpodman machineVMs (#23277). - The
podman images --sort=repositorycommand now also sorts by image tag as well, guaranteeing deterministic output ordering (#23803). - When a user has a rootless
podman machineVM running and second rootfulpodman machineVM initialized, and the rootless VM is removed, the connection to the second, rootful machine now becomes the default as expected (#22577). - Environment variable secrets are no longer contained in the output of
podman inspecton a container the secret is used in (#23788). - Podman no longer exits 0 on SIGTERM by default.
- Podman no longer explicitly sets rlimits to their default value, as this could lower the actual value available to containers if it had been set higher previously.
- Quadlet user units now correctly wait for the network to be ready to use via a new service,
podman-user-wait-network-online.service, instead of the user session's nonfunctionalnetwork-online.target. - Exposed ports in the output of
podman psare now correctly grouped and deduplicated when they are also published (#23317). - Quadlet build units no longer use
RemainAfterExit=yesby default.
Bugfixes
- Fixed a bug where the
--build-contextoption topodman builddid not function properly on Windows, breaking compatibility with Visual Studio Dev Containers (#17313). - Fixed a bug where Quadlet would generate bad arguments to Podman if the
SecurityLabelDisableorSecurityLabelNestedkeys were used (#23432). - Fixed a bug where the
PODMAN_COMPOSE_WARNING_LOGSenvironment variable did not suppress warnings printed bypodman composethat it was redirecting to an external provider. - Fixed a bug where, if the
podman container cleanupcommand was run on a container in the process of being removed, an error could be printed. - Fixed a bug where rootless Quadlet units placed in
/etc/containers/systemd/users/would be loaded for root as well when/etc/containers/systemdwas a symlink (#23483). - Fixed a bug where the remote Podman client's
podman stopcommand would, if called with--cidfilepointing to a non-existent file and the--ignoreoption set, stop all containers (#23554). - Fixed a bug where the
podman waitwould only exit only after 20 second when run on a container which rapidly exits and is then restarted by theon-failurerestart policy. - Fixed a bug where
podman volume rmandpodman run -vcould deadlock when run simultaneously on the same volume (#23613). - Fixed a bug where running
podman mounton a container in the process of being created could cause a nonsensical error indicating the container already existed (#23637). - Fixed a bug where the
podman stopcommand could deadlock when run on containers with very large annotations (#22246). - Fixed a bug where the
podman machine stopcommand could segfault on Mac when a VM failed to stop gracefully (#23654). - Fixed a bug where the
podman stopcommand would not ensure containers created with--rmwere removed when it exited (#22852). - Fixed a bug where the
--rmioption topodman rundid not function correctly with detached containers. - Fixed a bug where running
podman inspecton a container on FreeBSD would emit an incorrect value for theHostConfig.Devicefield, breaking compatibility with the Ansible Podman module. - Fixed a bug where rootless Podman could fail to start containers using the
--cgroup-parentoption (#23780). - Fixed a bug where the
podman build -vcommand did not properly handle Windows paths passed as the host directory. - Fixed a bug where Podman could leak network namespace files if it was interrupted while creating a network namespace (#24044).
- Fixed a bug where the remote Podman client's
podman runcommand could sometimes fail to retrieve a container's exit code for containers run with the--rmoption. - Fixed a bug where
podman machineon Windows could fail to run VMs for certain usernames containing special characters. - Fixed a bug where Quadlet would reject
RemapUsers=keep-idwhen run as root. - Fixed a bug where XFS quotas on volumes were not unique, meaning that all volumes using a quota shared the same maximum size and inodes (set by the most recent volume with a quota to be created).
- Fixed a bug where
Servicesection of Quadlet files would only use defaults and not respect user input (#24322). - Fixed a bug where
podman volume lswould sometimes fail when a volume was removed at the same time it was run. - Fixed a bug where the
--tz=localoption could not be used when theTZDIRenvironment variable was set.
API
- The Play API for Kubernetes YAML now supports
application/x-tarcompressed context directories (#24015). - Fixed a bug in the Attach API for Containers (for both Compat and Libpod endpoints) which could cause inconsistent failures due to a race condition (#23757).
- Fixed a bug where the output for the Compat Top API for Containers did not properly split the output into an array (#23981).
- Fixed a bug where the Info API could fail when running
podman system servicevia a socket-activated systemd service (#24152). - Fixed a bug where the Events and Logs endpoints for Containers now send status codes immediately, as opposed to when the first event or log line is sent (#23712).
Misc
- Podman now requires Golang 1.22 or higher to build.
- The output of
podman machine starthas been improved when trying to start a machine when another is already running (#23436). - Quadlet will no longer log spurious ENOENT errors when resolving unit directories (#23620).
- The Docker alias shell script will now also honor the presence of
$XDG_CONFIG_HOME/containers/nodockerwhen considering whether it should print its warning message that Podman is in use. - The podman-auto-update systemd unit files have been moved into the
contrib/systemd/systemdirectory in the repo for consistency with our other unit files. - Updated Buildah to v1.38.0
- Updated the containers/common library to v0.61.0
- Updated the containers/storage library to v1.56.0
- Updated the containers/image library to v5.33.0
Known Issues
- The Podman installer for Windows will install WSLv2 even when Podman is configured to use the Hyper-V backend.
- Certain SSH configurations may make it impossible to connect to a
podman machineVM. A workaround is available in this issue. - The
libkrunVM provider for Mac is presently unusable on systems with 64gb or more of RAM.
We expect a Podman v5.3.1 release early next week with fixes for these issues.