[taler-deployment] 01/02: buildbot: enable host network loopback from podman

[gnunet]

This is an automated email from the git hooks/post-receive script.

devan-carpenter pushed a commit to branch master
in repository deployment.

commit 4190098c952a8ec238e1e8b16a25364bdf498611
Author: Devan Carpenter <devan@taler.net>
AuthorDate: Thu Oct 5 15:01:39 2023 -0400

    buildbot: enable host network loopback from podman
---
 buildbot/master.cfg | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/buildbot/master.cfg b/buildbot/master.cfg
index 835ad33..85bf697 100644
--- a/buildbot/master.cfg
+++ b/buildbot/master.cfg
@@ -196,6 +196,8 @@ def container_add_step(HALT_ON_FAILURE,
                 name=stepName,
                 commands=[
                     util.ShellArg(command=["podman", "run", "--rm",
+                                           "--add-host", 
"taler.host.internal:10.0.2.2",
+                                           "--network", 
"slirp4netns:allow_host_loopback=true",
                                            "--volume", f"{WORK_DIR}:/workdir",
                                            "--volume", 
"/home/container-worker/container_artifacts:/artifacts",
                                            "--workdir", "/workdir",
@@ -214,6 +216,8 @@ def container_add_step(HALT_ON_FAILURE,
                                            "-f", containerFile, "."],
                                   logname='build container', 
haltOnFailure=True),
                     util.ShellArg(command=["podman", "run", "--rm",
+                                           "--add-host", 
"taler.host.internal:10.0.2.2",
+                                           "--network", 
"slirp4netns:allow_host_loopback=true",
                                            "--volume", f"{WORK_DIR}:/workdir",
                                            "--volume", 
"/home/container-worker/container_artifacts:/artifacts",
                                            "--workdir", "/workdir",

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.