Skip to content

container: Exposed (bridged) mode

Currently the container spawns connected to its host through a dedicated network.

Container ---(fbx-testing-shared network)--- Host ---(LAN)--- router ---(Internet)

The container can open connections to the internet, but cannot expose services (to the internet).

I'd like to be able to spawn a container in a mode that exposes it to a network available to the host as if it were just another sister machine to the host.

Container -- |
Host      -- |---(LAN)--- router ---(Internet)
Others    -- |

This should enable us to expose services from the container to the internet (either through NAT or DMZ).

  • This should make testing of email server easier (email traffic patterns between email servers are complex and mocking everything correctly is difficult).
  • Another use case would be to enable other systemd non-Debian machines to 'install' freedombox (not just for development, but also for regular service). FreedomBox over Fedora/RHEL/Suse/...
  • Also Debian machines could deploy it this way. Some users might be able to play with it in their Desktops like developers do now. Others might squeeze FreedomBox along with other services reusing a single physical machine. We currently recommend to use a pristine Debian to deploy FreedomBox to avoid interferences. This might help to avoid that need in quite a few cases.