mirror of
https://github.com/containers/podman
synced 2024-10-19 08:44:11 +00:00
7b4102ce28
Both Podman and CRI-O set up CNI bridges with the name 'cni0'. If both our CNI conflist and the CRI-O conflist are installed, whoever runs first will win - that is, they will configure the bridge, and everyone will use it. Problem: the CRI-O CNI config conflicts with ours and results in containers with no networking. Solution: rename our bridge so we don't conflict with CRI-O. At the same time, hit our IPAM configuration. The current version was an older format in danger of deprecation. The new format is documented at [1]. Finally, fix indentation for the entire file. [1] https://github.com/containernetworking/plugins/tree/master/plugins/ipam/host-local#example-configurations Signed-off-by: Matthew Heon <matthew.heon@pm.me>
39 lines
603 B
Plaintext
39 lines
603 B
Plaintext
{
|
|
"cniVersion": "0.4.0",
|
|
"name": "podman",
|
|
"plugins": [
|
|
{
|
|
"type": "bridge",
|
|
"bridge": "cni-podman0",
|
|
"isGateway": true,
|
|
"ipMasq": true,
|
|
"ipam": {
|
|
"type": "host-local",
|
|
"routes": [
|
|
{
|
|
"dst": "0.0.0.0/0"
|
|
}
|
|
],
|
|
"ranges": [
|
|
[
|
|
{
|
|
"subnet": "10.88.0.0/16",
|
|
"gateway": "10.88.0.1"
|
|
}
|
|
]
|
|
]
|
|
}
|
|
},
|
|
{
|
|
"type": "portmap",
|
|
"capabilities": {
|
|
"portMappings": true
|
|
}
|
|
},
|
|
{
|
|
"type": "firewall",
|
|
"backend": "iptables"
|
|
}
|
|
]
|
|
}
|