From 59d16b9ad7b5ee5f72a9f0b433c6a5d78a03d5d4 Mon Sep 17 00:00:00 2001 From: Philip Durbin Date: Thu, 21 Mar 2024 16:04:32 -0400 Subject: [PATCH] clarify how to increase timeout in docker demo #10409 --- doc/sphinx-guides/source/container/running/demo.rst | 8 +++++++- docker/compose/demo/compose.yml | 2 ++ 2 files changed, 9 insertions(+), 1 deletion(-) diff --git a/doc/sphinx-guides/source/container/running/demo.rst b/doc/sphinx-guides/source/container/running/demo.rst index 24027e677a1..2991c677618 100644 --- a/doc/sphinx-guides/source/container/running/demo.rst +++ b/doc/sphinx-guides/source/container/running/demo.rst @@ -59,6 +59,8 @@ Edit the ``compose.yml`` file and look for the following section. container_name: "bootstrap" image: gdcc/configbaker:alpha restart: "no" + environment: + - TIMEOUT=3m command: - bootstrap.sh - dev @@ -189,13 +191,17 @@ Windows support is experimental but we are very interested in supporting Windows Bootstrapping Did Not Complete ++++++++++++++++++++++++++++++ -In the compose file, try increasing the timeout in the bootstrap container by adding something like this: +In the compose file, try increasing the timeout for the bootstrap container: .. code-block:: bash environment: - TIMEOUT=10m +As described above, you'll want to stop containers, delete data, and start over with ``docker compose up``. To make sure the increased timeout is in effect, you can run ``docker logs bootstrap`` and look for the new value in the output: + +``Waiting for http://dataverse:8080 to become ready in max 10m.`` + Wrapping Up ----------- diff --git a/docker/compose/demo/compose.yml b/docker/compose/demo/compose.yml index e4bcc9778d7..8f1af3e396b 100644 --- a/docker/compose/demo/compose.yml +++ b/docker/compose/demo/compose.yml @@ -49,6 +49,8 @@ services: container_name: "bootstrap" image: gdcc/configbaker:alpha restart: "no" + environment: + - TIMEOUT=3m command: - bootstrap.sh - dev