podman4: network-usage blog update install instructions #509
Conversation
|
@lsm5 PTAL |
|
LGTM |
|
netavark is a |
|
@lsm5 The problem is not that aardvark is not pulled in, the thing is that netvark is not installed when you update because containernetworking-plugins is already present. |
Right, I'm not talking about aardvark either. What I meant was podman4 upgrade should trigger a containers-common upgrade which should pull in netavark, unless they have set Recommends to not be installed by default. Regardless, the explicit installation step doesn't hurt. |
|
@TomSweeneyRedHat PTAL |
|
Ah I see now. I guess you are right and the user didn't had the recommends installed. |
_posts/2022-02-04-network-usage.md
Outdated
| @@ -36,5 +36,7 @@ Add the podman4 test COPR to your system | |||
| If you have never installed Podman, replace `upgrade` with `install` in the following command. | |||
| > $ sudo dnf upgrade podman | |||
|
|
|||
| If you find bugs, please report them to our [github issues page](https://github.com/containers/podman/issues). | |||
| If podman was upgraded, you have to install netavark explicitly otherwise the package will keep using CNI and does not install netavark. | |||
There was a problem hiding this comment.
| If podman was upgraded, you have to install netavark explicitly otherwise the package will keep using CNI and does not install netavark. | |
| If Podman was upgraded, you have to install netavark explicitly. Otherwise, the Podman package will continue to use CNI. |
The podman package will not install netavark when CNI is already installed. Ref: containers/podman#11719 (comment) Signed-off-by: Paul Holzinger <[email protected]>
The podman package will not install netavark when CNI is already
installed.
Ref: containers/podman#11719 (comment)