8000 F36: CHANGE: Podman 4.0 · Issue #1106 · coreos/fedora-coreos-tracker · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

F36: CHANGE: Podman 4.0 #1106

Closed
dustymabe opened this issue Feb 16, 2022 · 8 comments
Closed

F36: CHANGE: Podman 4.0 #1106

dustymabe opened this issue Feb 16, 2022 · 8 comments

Comments

@dustymabe
Copy link
Member

In the 2022-02-16 community meeting we decided to open a ticket for podman v4 in FCOS.

  • Podman 4.0
    • Podman 4.0 will be released in Fedora 36 for the first time.
    • Tracking bug: #2052692
@dustymabe
Copy link
Member Author

Note this is related to the request to ship podman 4.0 in F35 as well: #1070

@dustymabe
Copy link
Member Author

The current action item here is:

12:35:48       dustymabe | #action jlebon to send out an announcement about
                         | podmanv4 coming to F36 and the beta coming to next in
                         | the coming weeks

Basically we need to come up with a summary of the breaking changes so our users have notice before the F36 beta lands in next.

@travier
Copy link
Member
travier commented Feb 23, 2022

Should I write a short guide using https://copr.fedorainfracloud.org/coprs/rhcontainerbot/podman4/ to let users try podman v4 on FCOS ahead of the f36 rebase?

@dust
8000
ymabe
Copy link
Member Author

Seems like it could be a good thing 👍

@jlebon
Copy link
Member
jlebon commented Feb 23, 2022

Wrote up a draft email in https://hackmd.io/fw3O4MYgTECcuq1cYLeTMg. Feel free to edit/tweak.

@dustymabe
Copy link
Member Author

communication sent out:

@dustymabe
Copy link
Member Author

next has been on a Fedora 36 base for a few weeks now. So far no issues reported. One test that will be telling is if we can still use gangplank to do builds (we might be using some of the APIs that have backwards incompatible changes).

@dustymabe
Copy link
Member Author

I verified today that we can still use gangplank to do builds by spinning up our aarch64 builder against the next stream. Seems to be working great so far.

Considering we've seen no issues so far I'm going to close this one out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants
0