podman/cni/87-podman-bridge.conflist

{
    "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"
	}
    ]
}
Enable port bindings Set up nbetworking ports for the following use cases: * bind the same port between host and container * bind a specific host port to a different container port * bind a random host port to a specific container port Signed-off-by: baude <bbaude@redhat.com> Closes: #214 Approved by: baude 2018-01-04 18:59:33 +00:00			`{`
networking: use firewall plugin drop the pkg/firewall module and start using the firewall CNI plugin. It requires an updated package for CNI plugins. Signed-off-by: Giuseppe Scrivano <gscrivan@redhat.com> 2019-04-15 12:16:34 +00:00			`"cniVersion": "0.4.0",`
Enable port bindings Set up nbetworking ports for the following use cases: * bind the same port between host and container * bind a specific host port to a different container port * bind a random host port to a specific container port Signed-off-by: baude <bbaude@redhat.com> Closes: #214 Approved by: baude 2018-01-04 18:59:33 +00:00			`"name": "podman",`
			`"plugins": [`
Adjust name of Podman CNI network bridge 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> 2019-08-07 18:29:20 +00:00			`{`
			`"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"`
			`}`
Enable port bindings Set up nbetworking ports for the following use cases: * bind the same port between host and container * bind a specific host port to a different container port * bind a random host port to a specific container port Signed-off-by: baude <bbaude@redhat.com> Closes: #214 Approved by: baude 2018-01-04 18:59:33 +00:00			`]`
			`}`