Skip to content

Conversation

@baude
Copy link
Member

@baude baude commented Sep 10, 2025

Adding a design document for Podman 6. it is a high level design that tries to encompasses proposed changes to Podman and its runtime environment. It should highlight major changes and features; but you will also find nitty detailed changes that have been idenitified. It is quite possible things in this document will change but it allows for open, transparent communication.

Does this PR introduce a user-facing change?

None

@openshift-ci openshift-ci bot added release-note-none approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 10, 2025
@baude
Copy link
Member Author

baude commented Sep 10, 2025

i did this from a google doc export but it makes paragraphs one per line. Do folks think i should employ line breaks at say 100 chars or so ?

@mheon
Copy link
Member

mheon commented Sep 10, 2025

I usually do a line break every sentence, but 100 chars also works fine

Copy link
Member

@Luap99 Luap99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I agree more line breaks would be nice but that should not matter when viewing in the rendered form so I don't care much.


## **Slirp4netns**

[Slipr4netns](https://github.com/rootless-containers/slirp4netns) was the original network utility for rootless Podman and has been replaced by [Pasta](https://passt.top/passt/about/). Podman has been able to use Pasta since version 4.4. In Podman 5.0, Pasta became the default rootless option and a deprecation notice for slirp4netns was made in Podman 5\.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a deprecation notice for slirp4netns was made in Podman 5

The text looks good but I'm curious where to find the deprecation notice. I searched in https://github.com/containers/podman/blob/main/RELEASE_NOTES.md
but couldn't find it. I also did some recursive grep

grep -ri slirp4netns docs/
grep -ri deprecat docs/

Maybe I just missed it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i wonder if it got wacked between 4 and 5? @mheon are you aware ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll have to go looking. It might have just gone out in a blog post, which could be an issue. We can include a formal reminder in the 5.7 release notes, which still gives 6 months notice?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can include a formal reminder in the 5.7 release notes, which still gives 6 months notice?

sgtm

@mheon
Copy link
Member

mheon commented Sep 25, 2025

We should merge this and the Conmonv3 doc this week, we've given plenty of time for review

Adding a design document for Podman 6.  it is a high level design that tries to encompasses proposed changes to Podman and its runtime environment.  It should highlight major changes and features; but you will also find nitty detailed changes that have been idenitified.  It is quite possible things in this document will change but it allows for open, transparent communication.

Signed-off-by: Brent Baude <bbaude@redhat.com>
@baude
Copy link
Member Author

baude commented Sep 25, 2025

updated with comment fixes and added line breaks

@mheon
Copy link
Member

mheon commented Sep 25, 2025

/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 25, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: baude, mheon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit a118fdf into containers:main Sep 25, 2025
33 of 40 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. release-note-none

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants