Pulp-container

Latest version: v2.24.1

Safety actively analyzes 714860 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 16 of 24

2.9.3

Not secure
Bugfixes

- Fixed file descriptor leak during image push.
[523](https://github.com/pulp/pulp_container/issues/523)
- Fixed error during container image push.
[542](https://github.com/pulp/pulp_container/issues/542)
- Fixed rate_limit option on the remote. Rate limit defines N req/sec per connection.
[578](https://github.com/pulp/pulp_container/issues/578)
- Fixed a bug that caused container clients to be unable to interact with content stored on S3.
[579](https://github.com/pulp/pulp_container/issues/579)

---

2.9.2

Not secure
Bugfixes

- Added validation for the supported manifests and blobs media_types in the push operation.
[8303](https://pulp.plan.io/issues/8303)
- Fixed ORM calls in the content app that were made in async context to use sync_to_async.
[9454](https://pulp.plan.io/issues/9454)
- Fixed a failure during distribution update that occured when unsetting repository_version.
[9497](https://pulp.plan.io/issues/9497)
- Corrected value of `Content-Length` header for push upload responses.
This fixes the *upstream prematurely closed connection while reading upstream* error that would
appear in nginx logs after a push operation.
[9516](https://pulp.plan.io/issues/9516)
- Fixed headers and status codes in the upload/blob responses during image push.
[9568](https://pulp.plan.io/issues/9568)
- Send proper blob content_type header when the blob is served.
[9571](https://pulp.plan.io/issues/9571)
- Fixed a bug that caused container clients to be unable to interact with content stored on S3.
[9586](https://pulp.plan.io/issues/9586)
- Fixed a bug, where permissions were checked against the wrong object type.
[9589](https://pulp.plan.io/issues/9589)

Misc

- [9562](https://pulp.plan.io/issues/9562), [#9618](https://pulp.plan.io/issues/9618)

---

2.9.1

Not secure
Bugfixes

- Fixed ORM calls in the content app that were made in async context to use sync_to_async.
(Backported from <https://pulp.plan.io/issues/9454>).
[9538](https://pulp.plan.io/issues/9538)
- Corrected value of `Content-Length` header for push upload responses.
This fixes the *upstream prematurely closed connection while reading upstream* error that would
appear in nginx logs after a push operation (Backported from <https://pulp.plan.io/issues/9516>).
[9539](https://pulp.plan.io/issues/9539)
- Fixed Azure storage backend support (Backported from <https://pulp.plan.io/issues/9488>).
[9540](https://pulp.plan.io/issues/9540)

---

2.9.0

Not secure
Bugfixes

- Switched from `condition` element to `condition_expression` for boolean logic evaluation to
support latest drf-access-policy.
[9092](https://pulp.plan.io/issues/9092)
- Fix OpenAPI schema view
[9258](https://pulp.plan.io/issues/9258)
- Refactor sync pipeline to fix a race condition with multiple synchronous syncs.
[9292](https://pulp.plan.io/issues/9292)
- Added validation for a repository base path.
[9403](https://pulp.plan.io/issues/9403)

Misc

- [9187](https://pulp.plan.io/issues/9187), [#9203](https://pulp.plan.io/issues/9203), [#9310](https://pulp.plan.io/issues/9310), [#9385](https://pulp.plan.io/issues/9385), [#9466](https://pulp.plan.io/issues/9466)

---

2.8.9

Not secure
Bugfixes

- Fixed a bug that led Pulp to run out of DB connections during podman pull operations.
[1146](https://github.com/pulp/pulp_container/issues/1146)

---

2.8.8

Not secure
Bugfixes

- Fixed an HTTP 404 response during sync from registry.redhat.io.
[974](https://github.com/pulp/pulp_container/issues/974)

---

Page 16 of 24

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.