Paul Holzinger 24bec9a76b default network: do not validate the used subnets ... The default network should not be validated against used subnets, we have to ensure that this network can always be created even when a subnet is already used on the host. This could happen if you run a container on this net, then the cni interface will be created on the host and "block" this subnet from being used again. Therefore the next podman command tries to create the default net again and it would fail because it thinks the network is used on the host. Signed-off-by: Paul Holzinger <pholzing@redhat.com>		2021-09-15 18:05:26 +02:00
..
cni	default network: do not validate the used subnets	2021-09-15 18:05:26 +02:00
types	Network interface	2021-08-24 12:28:03 +02:00
util	Network interface	2021-08-24 12:28:03 +02:00
config.go	Fix network create macvlan with subnet option	2021-05-20 13:12:01 +02:00
create.go	Detect if in podman machine virtual vm	2021-04-30 13:11:05 -05:00
create_test.go	bump go module to v3	2021-02-22 09:03:51 +01:00
devices.go	Drop dependency on iproute	2021-09-02 10:28:08 +02:00
files.go	Split libpod/network package	2021-03-15 14:01:52 +01:00
ip.go	prevent unpredictable results with network create|remove	2020-10-07 10:03:21 -05:00
lock.go	Move the cni lock file into the cni config dir	2021-01-21 11:50:45 +01:00
netconflist.go	Fix network create macvlan with subnet option	2021-05-20 13:12:01 +02:00
netconflist_test.go	Enable whitespace linter	2021-02-11 23:01:56 +01:00
network.go	Drop dependency on iproute	2021-09-02 10:28:08 +02:00
network_test.go	prevent unpredictable results with network create|remove	2020-10-07 10:03:21 -05:00
subnet.go	Fix ip-range for classless subnet masks	2020-11-23 11:55:29 +01:00
subnet_test.go	Fix ip-range for classless subnet masks	2020-11-23 11:55:29 +01:00