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

Upgrade to Podman 2.1 #9638

Closed
afbjorklund opened this issue Nov 8, 2020 · 2 comments
Closed

Upgrade to Podman 2.1 #9638

afbjorklund opened this issue Nov 8, 2020 · 2 comments
Assignees
Labels
co/runtime/crio CRIO related issues kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone

Comments

@afbjorklund
Copy link
Collaborator

We are currently running Podman 1.9

Once 2.1 is stable, we could upgrade

@afbjorklund afbjorklund added kind/feature Categorizes issue or PR as related to a new feature. co/runtime/crio CRIO related issues labels Nov 8, 2020
@afbjorklund afbjorklund changed the title Upgrade to Podman 2.1.x Upgrade to Podman 2.1 Nov 8, 2020
@RA489
Copy link

RA489 commented Nov 12, 2020

/assign

@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Nov 12, 2020

This is just a placeholder for a future milestone, nothing that is decided yet (still bugs in 2.2.0)

@afbjorklund afbjorklund added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Nov 12, 2020
@afbjorklund afbjorklund added this to the v1.16.0 milestone Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/runtime/crio CRIO related issues kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants