Podman: A tool for managing OCI containers and pods.
APACHE-2.0 License
Bot releases are hidden (Show)
/home
(#23515).Published by mheon 2 months ago
Published by mheon 3 months ago
libkrun
as a backend for creating virtual machines on MacOS. The libkrun
backend has the advantage of allowing GPUs to be mounted into the virtual machine to accelerate tasks. The default backend remains applehv
..build
files, which allows images to be built by Quadlet and then used by Quadlet containers..container
files now support two new fields, LogOpt
to specify container logging configuration and StopSignal
to specify container stop signal (#23050)..container
and .pod
files now support a new field, NetworkAlias
, to add network aliases.container.d
, pod.d
) and truncated unit drop-ins (unit-.container.d
) (#23158).podman system check
, which will identify (and, if possible, correct) corruption within local container storage.podman machine reset
command will now reset all providers available on the current operating system (e.g. ensuring that both HyperV and WSL podman machine
VMs will be removed on Windows)..image
units now have a dependency on network-online.target
(#21873).--device
option to podman create
and podman run
is no longer ignored when --privileged
is also specified (#23132).podman start
and podman stop
commands no longer print the full ID of the pod started/stopped, but instead the user's input used to specify the pod (e.g. podman pod start b
will print b
instead of the pod's full ID) (#22590).podman machine
on Linux now use virtiofs
instead of 9p
for mounting host filesystems. Existing mounts will be transparently changed on machine restart or recreation. This should improve performance and reliability of host mounts. This requires the installation of virtiofsd
on the host system to function.--squash
and --layers=false
options to podman build
at the same time is now allowed.--volume-driver
option to podman machine init
is now deprecated.--sdnotify=healthy
option could panic when started (#22651).--sdnotify=healthy
option that exited quickly would sometimes return an error instead of notifying that the container was ready (#22760).podman system reset
command did not remove the containers/image blob cache (#22825).--cgroups=disabled
option was specified at container creation time (#20910)./etc/hosts
file in a container was not created with a newline at the end of the file (#22729).podman start
command could sometimes panic when starting a container in the stopped state.podman system renumber
command would fail if volumes existed when using the sqlite
database backend (#23052).podman container restore
command could not successfully restore a container in a pod.podman diff
would suggest using the --latest
option when using the remote Podman client (#23038).podman events
command was rarely unable to report errors that occurred (#23165).--cidfile
option.podman run
and podman start
commands could throw strange errors if another Podman process stopped the container at a midpoint in the process of starting (#23246).podman system service
command could leak a mount on termination.podman images
(#23120).podman auto-update
and podman system df
commands could fail when a container was removed while the command was running (#23279).podman machine init
command could panic when trying to decompress an empty file when preparing the VM image (#23281).podman ps --pod
and podman pod stats
commands could sometimes fail when a pod was removed while the command was running (#23282).podman stats
and podman pod stats
commands would sometimes exit with a container is stopped
error when showing all containers (or pod containers, for pod stats
) if a container stopped while the command was running (#23334).podman play kube
command could sometimes not properly clean up their network stacks (#21569).podman build
command when the -f
option is given, but points to a file that does not exist, have been improved (#22940).Published by mheon 3 months ago
This is the final release candidate for v5.2.0. Preliminary release notes follow.
libkrun
as a backend for creating virtual machines on MacOS. The libkrun
backend has the advantage of allowing GPUs to be mounted into the virtual machine to accelerate tasks. The default backend remains applehv
..build
files, which allows images to be built by Quadlet and then used by Quadlet containers..container
files now support two new fields, LogOpt
to specify container logging configuration and StopSignal
to specify container stop signal (#23050)..container
and .pod
files now support a new field, NetworkAlias
, to add network aliases.container.d
, pod.d
) and truncated unit drop-ins (unit-.container.d
) (#23158).podman system check
, which will identify (and, if possible, correct) corruption within local container storage.podman machine reset
command will now reset all providers available on the current operating system (e.g. ensuring that both HyperV and WSL podman machine
VMs will be removed on Windows)..image
units now have a dependency on network-online.target
(#21873).--device
option to podman create
and podman run
is no longer ignored when --privileged
is also specified (#23132).podman start
and podman stop
commands no longer print the full ID of the pod started/stopped, but instead the user's input used to specify the pod (e.g. podman pod start b
will print b
instead of the pod's full ID) (#22590).podman machine
on Linux now use virtiofs
instead of 9p
for mounting host filesystems. Existing mounts will be transparently changed on machine restart or recreation. This should improve performance and reliability of host mounts. This requires the installation of virtiofsd
on the host system to function.--squash
and --layers=false
options to podman build
at the same time is now allowed.--volume-driver
option to podman machine init
is now deprecated.--sdnotify=healthy
option could panic when started (#22651).--sdnotify=healthy
option that exited quickly would sometimes return an error instead of notifying that the container was ready (#22760).podman system reset
command did not remove the containers/image blob cache (#22825).--cgroups=disabled
option was specified at container creation time (#20910)./etc/hosts
file in a container was not created with a newline at the end of the file (#22729).podman start
command could sometimes panic when starting a container in the stopped state.podman system renumber
command would fail if volumes existed when using the sqlite
database backend (#23052).podman container restore
command could not successfully restore a container in a pod.podman diff
would suggest using the --latest
option when using the remote Podman client (#23038).podman events
command was rarely unable to report errors that occurred (#23165).--cidfile
option.podman run
and podman start
commands could throw strange errors if another Podman process stopped the container at a midpoint in the process of starting (#23246).podman system service
command could leak a mount on termination.podman images
(#23120).podman auto-update
and podman system df
commands could fail when a container was removed while the command was running (#23279).podman machine init
command could panic when trying to decompress an empty file when preparing the VM image (#23281).podman ps --pod
and podman pod stats
commands could sometimes fail when a pod was removed while the command was running (#23282).podman stats
and podman pod stats
commands would sometimes exit with a container is stopped
error when showing all containers (or pod containers, for pod stats
) if a container stopped while the command was running (#23334).podman play kube
command could sometimes not properly clean up their network stacks (#21569).podman build
command when the -f
option is given, but points to a file that does not exist, have been improved (#22940).Published by mheon 3 months ago
.build
files, which allows images to be built by Quadlet and then used by Quadlet containers..container
files now support two new fields, LogOpt
to specify container logging configuration and StopSignal
to specify container stop signal (#23050)..container
and .pod
files now support a new field, NetworkAlias
, to add network aliases.container.d
, pod.d
) and truncated unit drop-ins (unit-.container.d
) (#23158).podman system check
, which will identify (and, if possible, correct) corruption within local container storage.podman machine reset
command will now reset all providers available on the current operating system (e.g. ensuring that both HyperV and WSL podman machine
VMs will be removed on Windows)..image
units now have a dependency on network-online.target
(#21873).--device
option to podman create
and podman run
is no longer ignored when --privileged
is also specified (#23132).podman start
and podman stop
commands no longer print the full ID of the pod started/stopped, but instead the user's input used to specify the pod (e.g. podman pod start b
will print b
instead of the pod's full ID) (#22590).podman machine
on Linux now use virtiofs
instead of 9p
for mounting host filesystems. Existing mounts will be transparently changed on machine restart or recreation. This should improve performance and reliability of host mounts.--squash
and --layers=false
options to podman build
at the same time is now allowed.--volume-driver
option to podman machine init
is now deprecated.--sdnotify=healthy
option could panic when started (#22651).--sdnotify=healthy
option that exited quickly would sometimes return an error instead of notifying that the container was ready (#22760).podman system reset
command did not remove the containers/image blob cache (#22825).--cgroups=disabled
option was specified at container creation time (#20910)./etc/hosts
file in a container was not created with a newline at the end of the file (#22729).podman start
command could sometimes panic when starting a container in the stopped state.podman system renumber
command would fail if volumes existed when using the sqlite
database backend (#23052).podman container restore
command could not successfully restore a container in a pod.podman diff
would suggest using the --latest
option when using the remote Podman client (#23038).podman events
command was rarely unable to report errors that occurred (#23165).--cidfile
option.podman run
and podman start
commands could throw strange errors if another Podman process stopped the container at a midpoint in the process of starting (#23246).podman system service
command could leak a mount on termination.podman images
(#23120).podman auto-update
and podman system df
commands could fail when a container was removed while the command was running (#23279).podman machine init
command could panic when trying to decompress an empty file when preparing the VM image (#23281).podman ps --pod
and podman pod stats
commands could sometimes fail when a pod was removed while the command was running (#23282).podman stats
and podman pod stats
commands would sometimes exit with a container is stopped
error when showing all containers (or pod containers, for pod stats
) if a container stopped while the command was running (#23334).podman build
command when the -f
option is given, but points to a file that does not exist, have been improved (#22940).Published by mheon 3 months ago
This is the first release candidate of Podman v5.2.0. We are expecting final release at the end of this month after 3 RCs.
Preliminary release notes will be available next week with RC2.
Published by mheon 3 months ago
podman machine
volumes into the virtual machine when using the Apple hypervisor (#22569).podman top
would show the incorrect UID for processes in containers run in a user namespace (#22293)./etc/hosts
and /etc/resolv.conf
files in a container would be empty after restoring from a checkpoint (#22901).--pod-id-file
argument to podman run
and podman create
did not respect the pod's user namespace (#22931).CONTAINER_CONNECTION
environment variable would lead to a panic.podman machine
using the Apple hypervisor now wait 90 seconds before forcibly stopping the VM, matching the standard systemd shutdown timeout (#22515).Published by mheon 5 months ago
Published by mheon 5 months ago
podman machine
on macOS with Apple silicon can now use Rosetta 2 (a.k.a Rosetta) for high-speed emulation of x86 code. This is enabled by default. If you wish to change this option, you can do so in containers.conf
.podman update
command are now persistent, and will survive container restart and be reflected in podman inspect
.podman update
command now includes a new option, --restart
, to update the restart policy of existing containers..container
files now support a new key, GroupAdd
, to add groups to the container.podman inspect
.podman run --mount type=image,...
now support a new option, subpath
, to mount only part of the image into the container.healthcheck_events
, has been added to containers.conf
under the [engine]
section to allow users to disable the generation of health_status
events to avoid spamming logs on systems with many healthchecks.io.podman.annotations.kube.image.automount/$CTRNAME
annotation (where $CTRNAME
is the name of the container they will be mounted into).podman info
command now includes the default rootless network command (pasta
or slirp4netns
).podman ps
command now shows ports from --expose
that have not been published with --publish-all
to improve Docker compatibility.podman runlabel
command now expands $HOME
in the label being run to the user's home directory.podman network list
, has been added to the podman network ls
command.podmansh
can now be set in containers.conf
.podman-setup.exe
Windows installer now provides 3 new CLI variables, MachineProvider
(choose the provider for the machine, windows
or wsl
, the default), HyperVCheckbox
(can be set to 1
to install HyperV if it is not already installed or 0
, the default, to not install HyperV), and SkipConfigFileCreation
(can be set to 1
to disable the creation of configuration files, or 0
, the default).podman kube play
that does not include an imagePullPolicy
and does not set a tag for the image, the image is now always pulled (#21211).podman kube play
, pod-level restart policies are now passed down to individual containers within the pod (#20903).--runroot
global option can now accept paths with lengths longer than 50 characters (#22272).podman update
command now emits an event.--userns=keep-id:uid=0
option to podman create
and podman run
would generate incorrect UID mappings and cause the container to fail to start (#22078).podman stats
could report inaccurate percentages for very large or very small values (#22064).rbind
instead of bind
, meaning recursive mounts were allowed by default (#22107).podman machine rm -f
command would fail to remove Hyper-V virtual machines if they were running.podman ps --sync
command could sometimes fail to properly update the status of containers.:idmap
option would sometimes be inaccessible with rootless Podman (#22228).:U
option would have their ownership changed to the owner of the directory in the image being mounted over (#22224).--force
option did not work when multiple arguments were given to the command and one of them did not exist (#21529).pause.pid
file in an incorrect directory (#22327).containers.conf
(#22561).podman kube down
command would not respect the StopTimeout
and StopSignal
of containers that it stopped (#22397).podman stop
finished stopping the container (#19629).podman farm build
command would not updating manifests on the registry that were already pushed (#22647).argv[0]
that is not a valid command path, as might happen when used in podmansh
(#22672).podman machine
connection URIs could be incorrect after an SSH port conflict, rendering machines inaccessible.podman events
command would not print an error if incorrect values were passed to its --since
and --until
options.host.containers.internal
entry could be added when running rootless containers using the bridge
network mode (#22653).podman machine
on Darwin systems when --log-level=debug
is used.EXTRA_BUILD_TAGS
environment variable.Published by mheon 5 months ago
This is the first release candidate for Podman v5.1.0. We expect the final release in 2 weeks (May 29 2024). Preliminary release notes follow.
podman update
command are now persistent, and will survive container restart and be reflected in podman inspect
.podman update
command now includes a new option, --restart
, to update the restart policy of existing containers..container
files now support a new key, GroupAdd
, to add groups to the container.podman inspect
.podman run --mount type=image,...
now support a new option, subpath
, to mount only part of the image into the container.healthcheck_events
, has been added to containers.conf
under the [engine]
section to allow users to disable the generation of health_status
events to avoid spamming logs on systems with many healthchecks.io.podman.annotations.kube.image.automount/$CTRNAME
annotation (where $CTRNAME
is the name of the container they will be mounted into).podman info
command now includes the default rootless network command (pasta
or slirp4netns
).podman ps
command now shows ports from --expose
that have not been published with --publish-all
to improve Docker compatibility.podman runlabel
command now expands $HOME
in the label being run to the user's home directory.podman network list
, has been added to the podman network ls
command.podman kube play
that does not include an imagePullPolicy
and does not set a tag for the image, the image is now always pulled (#21211).podman kube play
, pod-level restart policies are now passed down to individual containers within the pod (#20903).--runroot
global option can now accept paths with lengths longer than 50 characters (#22272).podman update
command now emits an event.--userns=keep-id:uid=0
option to podman create
and podman run
would generate incorrect UID mappings and cause the container to fail to start (#22078).podman stats
could report inaccurate percentages for very large or very small values (#22064).rbind
instead of bind
, meaning recursive mounts were allowed by default (#22107).podman machine rm -f
command would fail to remove Hyper-V virtual machines if they were running.podman ps --sync
command could sometimes fail to properly update the status of containers.:idmap
option would sometimes be inaccessible with rootless Podman (#22228).:U
option would have their ownership changed to the owner of the directory in the image being mounted over (#22224).--force
option did not work when multiple arguments were given to the command and one of them did not exist (#21529).pause.pid
file in an incorrect directory (#22327).containers.conf
(#22561).podman kube down
command would not respect the StopTimeout
and StopSignal
of containers that it stopped (#22397).podman stop
finished stopping the container (#19629).podman farm build
command would not updating manifests on the registry that were already pushed (#22647).argv[0]
that is not a valid command path, as might happen when used in podmansh
(#22672).podman machine
connection URIs could be incorrect after an SSH port conflict, rendering machines inaccessible.podman events
command would not print an error if incorrect values were passed to its --since
and --until
options.podman machine
on Darwin systems when --log-level=debug
is used.EXTRA_BUILD_TAGS
environment variable.Published by mheon 5 months ago
podman machine start
would fail if the machine had a volume with a long target path (#22226).podman machine start
mounted volumes with paths that included dashes in the wrong location (#22505).Published by mheon 6 months ago
:z
or :Z
volume mount options on a directory with read only files (#19852)Published by mheon 7 months ago
podman machine
VMs required an SSH client be installed on the system (#22075).podman build
command from working properly when connecting from a rootless client to a rootful server (#22109).podman machine
now fails immediately if admin privileges are not available (previously, it would only fail when it reached operations that required admin privileges).Published by mheon 7 months ago
podman build
which allowed a user to write files to the /
directory of the host machine if selinux was not enabled.Published by mheon 7 months ago
podman build
which allowed a user to write files to the /
directory of the host machine if selinux was not enabled.podman machine
can now use the native Apple hypervisor (applehv
) when run on MacOS.podman machine reset
, which will remove all existing podman machine
VMs and relevant configurations.podman manifest add
command now supports a new --artifact
option to add OCI artifacts to a manifest list.podman create
, podman run
, and podman push
commands now support the --retry
and --retry-delay
options to configure retries for pushing and pulling images.podman run
and podman exec
commands now support a new option, --preserve-fd
, which allows passing a list of file descriptors into the container (as an alternative to --preserve-fds
, which passes a specific number of file descriptors).podman kube play
command can now create image-based volumes using the volume.podman.io/image
annotation.podman kube play
can now include volumes from other containers (similar to the --volumes-from
option) using a new annotation, io.podman.annotations.volumes-from
(#16819).podman kube play
can now set user namespace options through the the io.podman.annotations.userns
annotation in the pod definition (#20658).containers.conf
field interface_name
(#21313).--gpus
option to podman create
and podman run
is now compatible with Nvidia GPUs (#21156).--mount
option to podman create
and podman run
supports a new mount option, no-dereference
, to mount a symlink (instead of its dereferenced target) into a container (#20098).--config
, to point to a Docker configuration where we can source registry login credentials.podman ps --format
command now supports a new format specifier, .Label
(#20957).uidmapping
and gidmapping
options to the podman run --userns=auto
option can now map to host IDs by prefixing host IDs with the @
symbol..pod
unit files (#17687).Entrypoint
and StopTimeout
, in .container
files (#20585 and #21134).Ulimit
key multiple times in .container
files to set more than one ulimit on a container.Notify
key to healthy
in .container
files, to only sdnotify that a container has started when its health check begins passing (#18189).podman machine
commands has seen extensive rewrites. Configuration files have changed format and VMs from Podman 4.x and earlier are no longer usable. podman machine
VMs must be recreated with Podman 5.podman machine init
command now pulls images as OCI artifacts, instead of using HTTP. As a result, a valid policy.json
file is required on the host. Windows and Mac installers have been changed to install this file.podman machine
on Mac. Instead, the native Apple hypervisor is supported.ConfigPath
and Image
fields are no longer provided by the podman machine inspect
command. Users can also no longer use {{ .ConfigPath }}
or {{ .Image }}
as arguments to podman machine inspect --format
.podman inspect
for containers has seen a number of breaking changes to improve Docker compatibility, including changing Entrypoint
from a string to an array of strings and StopSignal from an int to a string.podman inspect
command for containers now returns nil for healthchecks when inspecting containers without healthchecks.podman pod inspect
command now outputs a JSON array regardless of the number of pods inspected (previously, inspecting a single pod would omit the array).PODMAN_IGNORE_CGROUPSV1_WARNING
environment variable can be set to suppress warnings.slirp4netns
to pasta
for improved performance. As a result, networks named pasta
are no longer supported.--image
option replaces the now deprecated --image-path
option for podman machine init
.podman events --format "{{json .}}"
has been changed to improve Docker compatibility, including the time
and timeNano
fields (#14993).podman machine
VMs and the username used within the VM are now validated and must match this regex: [a-zA-Z0-9][a-zA-Z0-9_.-]*
.--annotation
to podman manifest annotate
and podman manifest add
, the --configmap
, --log-opt
, and --annotation
options to podman kube play
, the --pubkeysfile
option to podman image trust set
, the --encryption-key
and --decryption-key
options to podman create
, podman run
, podman push
and podman pull
, the --env-file
option to podman exec
, the --bkio-weight-device
, --device-read-bps
, --device-write-bps
--device-read-iops
, --device-write-iops
, --device
, --label-file
, --chrootdirs
, --log-opt
, and --env-file
options to podman create
and podman run
, and the --hooks-dir
and --module
global options.podman system reset
command no longer waits for running containers to gracefully stop, and instead immediately sends SIGKILL (#21874).podman network inspect
command now includes running containers using the network in its output (#14126).podman compose
command is now supported on non-AMD64/ARM64 architectures.podman machine
will now pass HTTP proxy environment variables into the VM for all providers.--no-trunc
option to the podman kube play
and podman kube generate
commands has been deprecated. Podman now complies to the Kubernetes specification for annotation size, removing the need for this option.DOCKER_HOST
environment variable will be set by default for rootless users when podman-docker is installed.podman system connection
and farms from podman farm
are now written to a new configuration file called podman-connections.conf
. As a result, Podman no longer writes to containers.conf
. Existing connections from containers.conf
will still be respected.podman farm
subcommands (save for podman farm build
) no longer need to connect to the machines in the farm to run.podman create
and podman run
commands no longer require specifying an entrypoint on the command line when the container image does not define one. In this case, an empty command will be passed to the OCI runtime, and the resulting behavior is runtime-specific.podman machine
VMs on Mac is now system_u:object_r:nfs_t:s0
so that it can be shared with all containers without issue.podman machine
will now share a single SSH key key for access. As a result, podman machine rm --save-keys
is deprecated as the key will persist by default.podman stats
command would not show network statistics when the pasta
network mode was used.podman machine
VMs using the HyperV provider could not mount shares on directories that did not yet exist.podman compose
command did not respect the --connection
and --url
options.podman stop -t -1
command would wait for 0 seconds, not infinite seconds, before sending SIGKILL (#21811).slirp4netns
network mode was used with a restart policy of always
or unless-stopped
or on-failure
and a user namespace (#21477).docker.sock
symlink (#20650).podman image scp
command could fail if there was not sufficient space in the destination machine's /tmp
for the image (#21239).podman inspect
(#13102).podman kube play
did not create memory-backed emptyDir volumes using a tmpfs filesystem.--rm
were sometimes not removed after a reboot (#21482).podman events
command using the remote Podman client did not display the network name associated with network events (#21311).podman farm build
did not properly handle the --tls-verify
option and would override server defaults even if the option was not set by the user (#21352).podman inspect
command could segfault on FreeBSD (#21117)..container
file with certain types of trailing whitespace (#21109).bind-mount-options
key (#21080)..container
files (#20992).--publish-all
option to podman kube play
did not function when used with the remote Podman client.podman kube play --build
command could not build images whose Dockerfile specified an image from a private registry with a self-signed certificate in a FROM
directive (#20890)./libpod/images/$name/resolve
, has been added to resolve a (potential) short name to a list of fully-qualified image references Podman which could be used to pull the image./etc/hosts
were copied into create containers, resulting in incompatibility with network aliases.podman build
.Published by mheon 7 months ago
This will be the final v5.0.0 release candidate. If all goes well, we expect a final release early next week. Release notes follow:
podman machine
can now use the native Apple hypervisor (applehv
) when run on MacOS.podman machine reset
, which will remove all existing podman machine
VMs and relevant configurations.podman manifest add
command now supports a new --artifact
option to add OCI artifacts to a manifest list.podman create
, podman run
, and podman push
commands now support the --retry
and --retry-delay
options to configure retries for pushing and pulling images.podman run
and podman exec
commands now support a new option, --preserve-fd
, which allows passing a list of file descriptors into the container (as an alternative to --preserve-fds
, which passes a specific number of file descriptors).podman kube play
command can now create image-based volumes using the volume.podman.io/image
annotation.podman kube play
can now include volumes from other containers (similar to the --volumes-from
option) using a new annotation, io.podman.annotations.volumes-from
(#16819).podman kube play
can now set user namespace options through the the io.podman.annotations.userns
annotation in the pod definition (#20658).containers.conf
field interface_name
(#21313).--gpus
option to podman create
and podman run
is now compatible with Nvidia GPUs (#21156).--mount
option to podman create
and podman run
supports a new mount option, no-dereference
, to mount a symlink (instead of its dereferenced target) into a container (#20098).--config
, to point to a Docker configuration where we can source registry login credentials.podman ps --format
command now supports a new format specifier, .Label
(#20957).uidmapping
and gidmapping
options to the podman run --userns=auto
option can now map to host IDs by prefixing host IDs with the @
symbol..pod
unit files (#17687).Entrypoint
and StopTimeout
, in .container
files (#20585 and #21134).Ulimit
key multiple times in .container
files to set more than one ulimit on a container.Notify
key to healthy
in .container
files, to only sdnotify that a container has started when its health check begins passing (#18189).podman machine
commands has seen extensive rewrites. Configuration files have changed format and VMs from Podman 4.x and earlier are no longer usable. podman machine
VMs must be recreated with Podman 5.podman machine init
command now pulls images as OCI artifacts, instead of using HTTP. As a result, a valid policy.json
file is required on the host. Windows and Mac installers have been changed to install this file.podman machine
on Mac. Instead, the native Apple hypervisor is supported.ConfigPath
and Image
fields are no longer provided by the podman machine inspect
command. Users can also no longer use {{ .ConfigPath }}
or {{ .Image }}
as arguments to podman machine inspect --format
.podman inspect
for containers has seen a number of breaking changes to improve Docker compatibility, including changing Entrypoint
from a string to an array of strings and StopSignal from an int to a string.podman inspect
command for containers now returns nil for healthchecks when inspecting containers without healthchecks.podman pod inspect
command now outputs a JSON array regardless of the number of pods inspected (previously, inspecting a single pod would omit the array).PODMAN_CGROUPSV1_WARNING
environment variable can be set to suppress warnings.slirp4netns
to pasta
for improved performance. As a result, networks named pasta
are no longer supported.--image
option replaces the now deprecated --image-path
option for podman machine init
.podman events --format "{{json .}}"
has been changed to improve Docker compatibility, including the time
and timeNano
fields (#14993).podman machine
VMs and the username used within the VM are now validated and must match this regex: [a-zA-Z0-9][a-zA-Z0-9_.-]*
.--annotation
to podman manifest annotate
and podman manifest add
, the --configmap
, --log-opt
, and --annotation
options to podman kube play
, the --pubkeysfile
option to podman image trust set
, the --encryption-key
and --decryption-key
options to podman create
, podman run
, podman push
and podman pull
, the --env-file
option to podman exec
, the --bkio-weight-device
, --device-read-bps
, --device-write-bps
--device-read-iops
, --device-write-iops
, --device
, --label-file
, --chrootdirs
, --log-opt
, and --env-file
options to podman create
and podman run
, and the --hooks-dir
and --module
global options.podman system reset
command no longer waits for running containers to gracefully stop, and instead immediately sends SIGKILL (#21874).podman network inspect
command now includes running containers using the network in its output (#14126).podman compose
command is now supported on non-AMD64/ARM64 architectures.podman machine
will now pass HTTP proxy environment variables into the VM for all providers.--no-trunc
option to the podman kube play
and podman kube generate
commands has been deprecated. Podman now complies to the Kubernetes specification for annotation size, removing the need for this option.DOCKER_HOST
environment variable will be set by default for rootless users when podman-docker is installed.podman system connection
and farms from podman farm
are now written to a new configuration file called podman-connections.conf
. As a result, Podman no longer writes to containers.conf
. Existing connections from containers.conf
will still be respected.podman farm
subcommands (save for podman farm build
) no longer need to connect to the machines in the farm to run.podman create
and podman run
commands no longer require specifying an entrypoint on the command line when the container image does not define one. In this case, an empty command will be passed to the OCI runtime, and the resulting behavior is runtime-specific.podman machine
VMs on Mac is now system_u:object_r:nfs_t:s0
so that it can be shared with all containers without issue.podman machine
will now share a single SSH key key for access. As a result, podman machine rm --save-keys
is deprecated as the key will persist by default.podman stats
command would not show network statistics when the pasta
network mode was used.podman machine
VMs using the HyperV provider could not mount shares on directories that did not yet exist.podman compose
command did not respect the --connection
and --url
options.podman stop -t -1
command would wait for 0 seconds, not infinite seconds, before sending SIGKILL (#21811).slirp4netns
network mode was used with a restart policy of always
or unless-stopped
or on-failure
and a user namespace (#21477).docker.sock
symlink (#20650).podman image scp
command could fail if there was not sufficient space in the destination machine's /tmp
for the image (#21239).podman inspect
(#13102).podman kube play
did not create memory-backed emptyDir volumes using a tmpfs filesystem.--rm
were sometimes not removed after a reboot (#21482).podman events
command using the remote Podman client did not display the network name associated with network events (#21311).podman farm build
did not properly handle the --tls-verify
option and would override server defaults even if the option was not set by the user (#21352).podman inspect
command could segfault on FreeBSD (#21117)..container
file with certain types of trailing whitespace (#21109).bind-mount-options
key (#21080)..container
files (#20992).--publish-all
option to podman kube play
did not function when used with the remote Podman client.podman kube play --build
command could not build images whose Dockerfile specified an image from a private registry with a self-signed certificate in a FROM
directive (#20890)./libpod/images/$name/resolve
, has been added to resolve a (potential) short name to a list of fully-qualified image references Podman which could be used to pull the image./etc/hosts
were copied into create containers, resulting in incompatibility with network aliases.podman build
.Published by ashley-cui 7 months ago
This is the sixth release candidate of Podman 5.0.0. Full release notes will be available soon.
Published by ashley-cui 7 months ago
This is the fifth release candidate of Podman 5.0.0. Full release notes will be available soon.
Published by lsm5 8 months ago
This is the fourth release candidate of Podman 5.0.0. Full release notes will be available soon.