Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created by
brew bump
Created with
brew bump-formula-pr
.resource
blocks have been checked for updates.release notes
containers.Commit()
function now returns a new struct (types.IDResponse
) with identical contents, and thecontainers.ExecCreate
function'shandlers.ExecCreateConfig
parameter now contains a different embedded struct, potentially requiring changes to how it is assigned to.Changes
stopped
, which is reported if the container the healthcheck was run on stopped before the check could be completed (#25276).podman machine
VMs with a host mount over the VM's/tmp
directory is no longer allowed (#18230).podman logs
command now allows options to be specified after the container name (e.g.podman logs $containername --follow
) (#25653).catatonit
binary will be used (#23292).podman system reset
command no longer removes the user'spodman.sock
API socket.dns.podman
added. Queries resolving such names will still work..network
unit will now delete the network (if no containers are actively using it) (#23678)./proc/interrupts
and/sys/devices/system/cpu/$CPU/thermal_throttle
paths are now masked by default in containers (#25634).Bugfixes
CAP_SYS_ADMIN
(#25241).podman exec
command would not add the additional groups of the user the exec session was run as unless the user was explicitly added with the--user
option (#25610).podman network connect
andpodman network disconnect
commands could create errors in the database which would causepodman inspect
on the container to fail.podman kube generate
command did not correctly generate YAML for volume mounts using a subpath.podman system df
command could show a negative reclaimable size.podman machine
VM that was notpodman-machine-default
(the default VM) with thepodman machine ssh
command would put the user into the rootless shell (#25332).podman machine init
would report nonsensical memory values in error messages when trying to create a machine with more memory than the system.podman start --attach
command would incorrectly print an error when run on a container created with the--rm
option (#25965).podman pull
command could hang and leak memory if the server was unexpectedly stopped or encountered an error during a pull.podman cp
command would, on Windows, often fail to copy files into the container due to improper handling of Windows paths (#14862).podman container clone
command did not correctly copy healthcheck settings to the new container (#21630).podman kube play
command would fail to start empty pods (#25786).podman volume ls
command did not output headers when no volumes were present (#25911).--health-cmd
option was specified when creating the container (#20212).--user
option topodman create
andpodman run
could not be used with users added to the container by the--hostuser
option (#25805).podman system reset
command on FreeBSD would incorrectly print an error.podman machine start
command with SIGINT could result in machine state being incorrectly set to "Starting" (#24416).podman machine start
command would fail when starting a VM with volume mounts containing spaces using the HyperV machine provider (#25500).API
Misc
ExecStartAndAttach()
function in the Go bindings for the REST API have been silenced, where the function would incorrectly report errors when stdin was consumed after the exec session was stopped (#25344).