containers
/
podman
mirror of https://github.com/containers/podman.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
8,269 Commits 52 Branches 247 Tags 253 MiB
Commit Graph

4 Commits

Author SHA1 Message Date
Maximilian Müller 48d83482db Use the libpod.conf cni_config_dir option for inspect and delete 
The pkg/network/files.go methods currently use the constant '/etc/cni/net.d'
for network handling. This results in the unability of podman-network-inspect
and podman-network-rm to locate the cni network configuration files.
This commit propagates the libpod.Runtime through the networking methods and
finally makes use of its configuration (config.Network.NetworkConfigDir).
Closes #6212

Signed-off-by: Maximilian Müller <maxm123@techie.com>
 2020-05-14 22:15:32 +02:00
baude 7343de24e5 check existing bridge names when creating networks 
when creating a new networking, we should check existing networks for
their bridge names and make sure the proposed new name is not part of
this. reported by QE.

Signed-off-by: baude <bbaude@redhat.com>
 2019-10-17 13:28:38 -05:00
baude b94ea07265 enhance podman network rm 
when removing a podman network, we need to make sure we delete the
network interface if one was ever created (by running a container).
also, when removing networks, we check if any containers are using the
network.  if they are, we error out unless the user provides a 'force'
option which will remove the containers in question.

Signed-off-by: baude <bbaude@redhat.com>
 2019-09-12 14:03:52 -05:00
baude ee432cf279 podman network create 
initial implementation of network create.  we only support bridging
networks with this first pass.

Signed-off-by: baude <bbaude@redhat.com>
 2019-09-09 09:32:43 -05:00