mirror of
https://github.com/containers/podman.git
synced 2025-09-16 22:34:51 +08:00
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>
This commit is contained in:
@ -344,10 +344,6 @@ func (ic *ContainerEngine) playKubePod(ctx context.Context, podName string, podY
|
||||
return nil, err
|
||||
}
|
||||
|
||||
if (ns.IsBridge() && len(networks) == 0) || ns.IsHost() {
|
||||
return nil, fmt.Errorf("invalid value passed to --network: bridge or host networking must be configured in YAML")
|
||||
}
|
||||
|
||||
podOpt.Net.Network = ns
|
||||
podOpt.Net.Networks = networks
|
||||
podOpt.Net.NetworkOptions = netOpts
|
||||
|
@ -165,8 +165,14 @@ EOF
|
||||
TESTDIR=$PODMAN_TMPDIR/testdir
|
||||
mkdir -p $TESTDIR
|
||||
echo "$testYaml" | sed "s|TESTDIR|${TESTDIR}|g" > $PODMAN_TMPDIR/test.yaml
|
||||
run_podman 125 kube play --network host $PODMAN_TMPDIR/test.yaml
|
||||
is "$output" ".*invalid value passed to --network: bridge or host networking must be configured in YAML" "podman plan-network should fail with --network host"
|
||||
run_podman kube play --network host $PODMAN_TMPDIR/test.yaml
|
||||
is "$output" "Pod:.*" "podman kube play should work with --network host"
|
||||
|
||||
run_podman pod inspect --format "{{.InfraConfig.HostNetwork}}" test_pod
|
||||
is "$output" "true" ".InfraConfig.HostNetwork"
|
||||
run_podman stop -a -t 0
|
||||
run_podman pod rm -t 0 -f test_pod
|
||||
|
||||
run_podman kube play --network slirp4netns:port_handler=slirp4netns $PODMAN_TMPDIR/test.yaml
|
||||
run_podman pod inspect --format {{.InfraContainerID}} "${lines[1]}"
|
||||
infraID="$output"
|
||||
|
Reference in New Issue
Block a user