From 5adfdee0d3cbcd27f194cd13496b9f7b49db9335 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Thomas=20Rame=CC=81?= <thomas@rame.fr>
Date: Mon, 14 Sep 2026 22:37:07 +0200
Subject: [PATCH] =?UTF-8?q?=F0=9F=90=9B(dev)=20missing=20default=20network?=
 =?UTF-8?q?=20for=20podman=20compose=20usage?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Some services, like celery-dev, attach to the `default` network
explicitly, next to `lasuite`. Docker compose creates that implicit
network on its own. Podman compose does not when the top-level
`networks` section is declared without it, so `compose up` failed on
the unknown `default` network.

Declare `default: {}` so that the network exists with both tools.
---
 compose.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/compose.yml b/compose.yml
index 7b4923247..d4ff490af 100644
--- a/compose.yml
+++ b/compose.yml
@@ -336,6 +336,7 @@ services:
       - "4000:3000"
 
 networks:
+  default: {}
   lasuite:
     name: lasuite-network
     driver: bridge