From 6cc9d8c72a56563b6d1a12b8b441dfa9dde345e9 Mon Sep 17 00:00:00 2001
From: Julien Dessaux
Date: Tue, 28 Apr 2020 17:29:52 +0200
Subject: Long overdue first commit with content

---
 content/en/blog/docker/docker-compose-bridge.md | 31 +++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100755 content/en/blog/docker/docker-compose-bridge.md

(limited to 'content/en/blog/docker/docker-compose-bridge.md')

diff --git a/content/en/blog/docker/docker-compose-bridge.md b/content/en/blog/docker/docker-compose-bridge.md
new file mode 100755
index 0000000..16a823d
--- /dev/null
+++ b/content/en/blog/docker/docker-compose-bridge.md
@@ -0,0 +1,31 @@
+---
+title: "Docker compose predictable bridge"
+linkTitle: "Docker compose predictable bridge"
+date: 2018-09-25
+description: >
+  How to use a predefined bridge with docker compose
+---
+
+By default, docker-compose will create a network with a randomly named bridge. If you are like me using a strict firewall on all your machines, this just cannot work.
+
+You need to put your services in `network_mode: “bridge”` and add a custom `network` entry like :
+
+{{< highlight yaml >}}
+version: '3.0'
+
+services:
+  sshportal:
+    image: moul/sshportal
+    environment:
+      - SSHPORTAL_DEFAULT_ADMIN_INVITE_TOKEN=integration
+    command: server --debug
+    depends_on:
+      - testserver
+    ports:
+      - 2222
+    network_mode: "bridge"
+networks:
+  default:
+    external:
+      name: bridge
+{{< /highlight >}}
-- 
cgit v1.2.3