[BUG] Documentation should mention creation of custom network

[GreenSkol]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hello,

After following the instructions, I faced the issue "Defined MONGO_HOST" is not reachable.

This was simply solved by creating a user-defined bridge network and configuring both containers to use it.

The root cause is that:

• the documentation doesn't mention connecting the Unifi & MongoDB containers to a user-defined network, resulting in the 2 container using the default bridge network and getting an automatically assigned IP.
• the documentation relies on container name resolution.
• the default bridge network doesn't support name resolution, which is highlighted in Docker documentation:

https://docs.docker.com/engine/network/drivers/bridge/

Expected Behavior

Following the documentation steps should work :-)

Steps To Reproduce

Follow the container installation documentation.

Environment

- OS:
- How docker service was installed:

CPU architecture

x86-64

Docker creation

Containers created using `docker create`

Container logs

$ docker logs -f unifi
[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    117
User GID:    1001
───────────────────────────────────────
Linuxserver.io version: 9.0.114-ls77
Build-date: 2025-02-04T16:51:55+00:00
───────────────────────────────────────
    
*** Waiting for MONGO_HOST mongo to be reachable. ***
*** Defined MONGO_HOST mongo is not reachable, cannot proceed. ***

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[Roxedus]

The reasoning here, is that docker compose creates a custom network automatically, and that compose is our recommended method of deployment.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[LinuxServer-CI]

This issue is locked due to inactivity