I’m working through this as well. I got the majority of the stack running using the docker-playground containers in host network mode as long as the Local/NIC IPs were correct in the configs. Still working on getting the ggsn connections right. A docker compose file would be helpful for sure. Matthew, do you have a write up, script or compose file that you could share with the community?
From: Matthew H <osmocom@marrold.co.uk>
Sent: Sunday, November 13, 2022 7:06:23 AM
To: Harald Welte <laforge@gnumonks.org>
Cc: openbsc@lists.osmocom.org <openbsc@lists.osmocom.org>
Subject: Re: Running Osmocom GSM stack in Docker
 
Hi Harald,

Thanks for the link, that's very helpful.

I started getting things setup with each component running in a
container with a statically assigned container, but I had issues with
SCTP between the MSC / BSC and STP (AS_DOWN). I'd see an INIT and INIT
ACK, but that was it, and nothing in the STP debug logs. Switching to
"Host" networking resolved the issue immediately after updating the
IPs in the various .cfgs back to 127.0.0.1. Perhaps it was a config
issue or something Docker related - I'm new to the Osmocom GSM stack
and SCTP in general so I'm not best suited for troubleshooting this,
but as its working with host networking I'll leave as-is

Thanks again
Matthew

On Sun, Nov 13, 2022 at 6:13 AM Harald Welte <laforge@gnumonks.org> wrote:
>
> See docker-playground.gir for Dockerfiles of all osmocom network elements. It is how our CI works.
>
> However, with all the 3GPP protocols there is none that you can speak through nat or even only with dynamic IPs.
>
> So the only way is to use  docker network with static IPs for each container.
> --
> Sent from a mobile device. Please excuse my brevity.