summaryrefslogtreecommitdiff
path: root/pkg/api/handlers/libpod/containers_stats.go
diff options
context:
space:
mode:
authorPaul Holzinger <pholzing@redhat.com>2022-09-29 16:59:35 +0200
committerPaul Holzinger <pholzing@redhat.com>2022-09-29 18:07:41 +0200
commitfe2b4df382a66889931a0158fc77d3235e00d8b8 (patch)
tree0b6293977bdf563ba67dcb17198d4003ea8e66d6 /pkg/api/handlers/libpod/containers_stats.go
parent4c39b391036c8383825b76ad0e2edf1efb53b4da (diff)
downloadpodman-fe2b4df382a66889931a0158fc77d3235e00d8b8.tar.gz
podman-fe2b4df382a66889931a0158fc77d3235e00d8b8.tar.bz2
podman-fe2b4df382a66889931a0158fc77d3235e00d8b8.zip
podman kube play allow --network host
I see no reason to block --network host with kube play and force users to have to set it in the yaml file. This is just confusing when compared to the other podman create/run --network options, see discussion in #15945. Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Diffstat (limited to 'pkg/api/handlers/libpod/containers_stats.go')
0 files changed, 0 insertions, 0 deletions