This lets you use -H unix://*.sock outside /var/run/weave. Using a socket directly in /var/run (i.e. /var/run/foo.sock), will reintroduce the bug with namespaces not being GCed, so that is a warning.
42 lines
1.5 KiB
Bash
Executable File
42 lines
1.5 KiB
Bash
Executable File
#! /bin/bash
|
|
|
|
. ./config.sh
|
|
|
|
start_suite "Various launch-proxy configurations"
|
|
|
|
# Booting it over unix socket listens on unix socket
|
|
run_on $HOST1 COVERAGE=$COVERAGE sudo -E weave launch-proxy
|
|
assert_raises "run_on $HOST1 sudo docker -H unix:///var/run/weave/weave.sock ps"
|
|
assert_raises "proxy docker_on $HOST1 ps" 1
|
|
weave_on $HOST1 stop-proxy
|
|
|
|
# Booting it over tcp listens on tcp
|
|
weave_on $HOST1 launch-proxy
|
|
assert_raises "run_on $HOST1 sudo docker -H unix:///var/run/weave/weave.sock ps" 1
|
|
assert_raises "proxy docker_on $HOST1 ps"
|
|
weave_on $HOST1 stop-proxy
|
|
|
|
# Booting it over tcp (no prefix) listens on tcp
|
|
DOCKER_CLIENT_ARGS="-H $HOST1:$DOCKER_PORT" $WEAVE launch-proxy
|
|
assert_raises "run_on $HOST1 sudo docker -H unix:///var/run/weave/weave.sock ps" 1
|
|
assert_raises "proxy docker_on $HOST1 ps"
|
|
weave_on $HOST1 stop-proxy
|
|
|
|
# Booting it with -H outside /var/run/weave, still works
|
|
socket="$(mktemp -d)/weave.sock"
|
|
weave_on $HOST1 launch-proxy -H unix://$socket
|
|
assert_raises "run_on $HOST1 sudo docker -H unix:///$socket ps" 0
|
|
weave_on $HOST1 stop-proxy
|
|
|
|
# Booting it over tls errors
|
|
assert_raises "DOCKER_CLIENT_ARGS='--tls' weave_on $HOST1 launch-proxy" 1
|
|
assert_raises "DOCKER_CERT_PATH='./tls' DOCKER_TLS_VERIFY=1 weave_on $HOST1 launch-proxy" 1
|
|
|
|
# Booting it with a specific -H overrides defaults
|
|
weave_on $HOST1 launch-proxy -H tcp://0.0.0.0:12345
|
|
assert_raises "run_on $HOST1 sudo docker -H tcp://$HOST1:12345 ps"
|
|
assert_raises "proxy docker_on $HOST1 ps" 1
|
|
weave_on $HOST1 stop-proxy
|
|
|
|
end_suite
|