Просмотр исходного кода

fix(start-console): use host networking on Linux

On Fedora 35, running `yarn run start-console` can result in network
unreachable errors with podman. Use host networking to avoid the problem.
Samuel Padgett 4 лет назад
Родитель
Сommit
053bbf4a97
1 измененных файлов с 9 добавлено и 2 удалено
  1. 9 2
      start-console.sh

+ 9 - 2
start-console.sh

@@ -23,9 +23,16 @@ echo "API Server: $BRIDGE_K8S_MODE_OFF_CLUSTER_ENDPOINT"
 echo "Console Image: $CONSOLE_IMAGE"
 echo "Console URL: http://localhost:${CONSOLE_PORT}"
 
+# Prefer podman if installed. Otherwise, fall back to docker.
 if [ -x "$(command -v podman)" ]; then
-    BRIDGE_PLUGINS="${npm_package_consolePlugin_name}=http://host.containers.internal:9001"
-    podman run --rm -p "$CONSOLE_PORT":9000 --env-file <(set | grep BRIDGE) $CONSOLE_IMAGE
+    if [ "$(uname -s)" = "Linux" ]; then
+        # Use host networking on Linux since host.containers.internal is unreachable in some environments.
+        BRIDGE_PLUGINS="${npm_package_consolePlugin_name}=http://localhost:9001"
+        podman run --rm --network=host --env-file <(set | grep BRIDGE) $CONSOLE_IMAGE
+    else
+        BRIDGE_PLUGINS="${npm_package_consolePlugin_name}=http://host.containers.internal:9001"
+        podman run --rm -p "$CONSOLE_PORT":9000 --env-file <(set | grep BRIDGE) $CONSOLE_IMAGE
+    fi
 else
     BRIDGE_PLUGINS="${npm_package_consolePlugin_name}=http://host.docker.internal:9001"
     docker run --rm -p "$CONSOLE_PORT":9000 --env-file <(set | grep BRIDGE) $CONSOLE_IMAGE