Closed baatl closed 6 months ago
Can you confirm if this is fixed in podman 5.0? We do not back port fixes to every distribution and hardly back port fixes to any distribution. (Red Hat employees do sometimes back port fixes to older RHEL versions, but even here we try to roll forward fairly agressively.) RHEL 9.4 will have podman 4.9 and RHEL 9.5 will have podman 5.*.
Ubuntu would have to rely on community people to backport fixes or update versions for use with Ubuntu.
I can try it on Fedora 39 with Podman 4.9.
Duplicate of #18077
Was fixed in https://github.com/containers/podman/pull/18078 (podman v4.5)
Issue Description
As previously filed in issue #9803 (Finding 4), which was prematurely closed after only Finding 1 (Volumes can not be created without a name) was resolved.
This impacts other downstream issues, such as containrrr/watchtower#1060.
This issue impacts the version of Podman that currently ships with the latest LTS release of Ubuntu (22.04): if this is fixed in a newer release, it would be useful for that fix to be backported (currently, the simplest fix for our use case was to abandon Podman altogether).
Steps to reproduce the issue
The API endpoint
/containers/create?name=
offers a wide range of settings for the new container. In theHostConfig
there is the subitemUlimits
which is a list of limits. If this subitem is present, the construction of the new container stops.payload.json
Describe the results you received
With
Ulimits
in theHostConfig
:If one deletes the
Ulimits
block from the payload the/create
call returns:Describe the results you expected
A test of the Docker API with
Ulimits
in theHostConfig
shows that the Docker API can create a new container withUlimits
.podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
No response
Additional information
No response