Connecting Docker/Portainer Networking Questions

I am using Rocky Linux on an extra PC at work, each one of my co-workers also have one.

I am trying to make a development server for Inductive Automation Ignition Containers
There is a main gateway, and then several edge devices that connect to that main gateway
I have Portainer installed, and I am trying to understand the networking in order to achieve my goal

I need all the Ignition Containers to be able to communicate with each other
I need to be able to customize the IP Addresses of each ignition container
Every Ignition Container must be able to use port 8088 (I suspect that I will use a macVLan for this)

I need to be able to connect to each of those edge devices as well as the main gateway using that custom IP from my Work PC

I need to isolate all the ignition instances and networking to be seperate from my Co-Workers Instances, as they will also have the same IP, but I want the containers to be independent

(This will be so we can version control our own environments)

Here’s a basic diagram of my goal, Any help with creating the networks, with the proper subnetworks, and visibility settings would be greatly appreciated, I’m sure that what I am trying to achieve should be possible, but I just need a little help getting there, thank you!

I’m not sure I could answer, so for now I changed the time interval to automatically close the topic after the last reply from 10 days to one month.

Your goal is probably not clear enough to users so you don’t get many replies.

Why would you need MacVLAN? Do you need to access the containers on LAN (from your PC) using a protocol that is not supported by reverese proxies?

Why would you need the same IP addresses? Isn’t it possible to have multiple dev environments where the IP addresses are coming from config files?

I just thought using a macVLan would make sense but honestly any way I could make this work I’d be all ears

Cany ou answer this one too?

The idea for the same ip addresses is to match a live environment server. So all of this is for a dev environment and having the ip configuration match is ideal so that way when uploaded from the dev to the live server you don’t need to change the config between the two