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.

Sign up for GitHub

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

Jump to bottom

Upgrade CNI to support version 0.4.0 #6664

Closed
afbjorklund opened this issue Feb 17, 2020 · 4 comments
Closed

Upgrade CNI to support version 0.4.0 #6664

afbjorklund opened this issue Feb 17, 2020 · 4 comments
Assignees
@afbjorklund
Labels
area/cni CNI support area/guest-vm General configuration issues with the minikube guest VM 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
v1.8.0 March 5

Comments

@afbjorklund
Copy link
Collaborator

ERRO[0000] Error adding network: incompatible CNI versions; config is "0.4.0", plugin supports ["0.1.0" "0.2.0" "0.3.0" "0.3.1"]

We are running 0.6.0 (Aug 2017), should upgrade to 0.7.0 (Apr 2019) - or 0.7.1

And we probably have to build it from source, in order to do so (no more binaries)

Required for podman run
@afbjorklund afbjorklund added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. area/guest-vm General configuration issues with the minikube guest VM area/cni CNI support labels Feb 17, 2020
@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Feb 17, 2020 •
edited
Loading

Related to #5822 and #5823

@afbjorklund afbjorklund self-assigned this Feb 17, 2020
@afbjorklund
Copy link
Collaborator Author

@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Feb 23, 2020 •
edited
Loading

If you want to run podman-remote run before this upgrade has landed, you can use --network=none or --network=host to avoid failing on the missing CNI default network (i.e./etc/cni/net.d/87-podman-bridge.conflist, the one that was failing to load with the error above)
Normally we only use podman-remote build and podman load, but it should be available...

@afbjorklund afbjorklund mentioned this issue Feb 24, 2020
Merged
@afbjorklund afbjorklund added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Feb 24, 2020
@afbjorklund
Copy link
Collaborator Author

afbjorklund commented Feb 24, 2020 •
edited
Loading

Not worth holding the release for, unless something else (than podman run) requires newer CRI ?

But confirmed that upgrading CNI and providing /etc/cni/net.d/87-podman-bridge.conflist fixes run

@afbjorklund afbjorklund added this to the v1.8.0 March 5 milestone Mar 8, 2020
This was referenced Apr 17, 2020
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@afbjorklund afbjorklund

Labels
area/cni CNI support area/guest-vm General configuration issues with the minikube guest VM 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
Milestone
v1.8.0 March 5
Development

No branches or pull requests
1 participant
@afbjorklund