[GH-ISSUE #3478] Netbird Peer/Client in Linux Docker Container > 0.31.0 -> unable to reach other Docker Containers with published Ports #7301

Open
opened 2026-08-05 01:12:23 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @yoobeedoobee on GitHub (Mar 10, 2025).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/3478

Originally assigned to: @nazarewk on GitHub.

Describe the problem

Netbird Peers in Linux Docker Container > 0.31.0 don't make other Docker Containers with published Ports accessible to logged in Desktop Peers

To Reproduce

Steps to reproduce the behavior:

  1. create a netbird client/peer with docker compose and add image 'netbirdio/netbird:latest'
  2. create another docker container on the same host with published port ie. 8888:80
  3. login with desktop peer@latest to self-hosted netbird@latest and try to reach container on the linux docker peer with published port

Expected behavior

Behaviour expected like with netbirdio/netbird:0.31.0, containers with published ports can be reached here. Starting from 0.32.0 this is not possible anymore.

Are you using NetBird Cloud?

self-host NetBird

NetBird version

latest, ie. 0.38.0

Is any other VPN software installed?

no

Debug output

To help us resolve the problem, please attach the following debug output

netbird status -dA -> unavailable for docker container peer

As well as the file created by

netbird debug for 1m -AS -> unavailable for docker container peer

Have you tried these troubleshooting steps?

  • [x ] Checked for newer NetBird versions
  • [x ] Searched for similar issues on GitHub (including closed ones)
  • [x ] Restarted the NetBird client
  • [x ] Disabled other VPN software
  • [x ] Checked firewall settings
Originally created by @yoobeedoobee on GitHub (Mar 10, 2025). Original GitHub issue: https://github.com/netbirdio/netbird/issues/3478 Originally assigned to: @nazarewk on GitHub. **Describe the problem** Netbird Peers in Linux Docker Container > 0.31.0 don't make other Docker Containers with published Ports accessible to logged in Desktop Peers **To Reproduce** Steps to reproduce the behavior: 1. create a netbird client/peer with docker compose and add image 'netbirdio/netbird:latest' 2. create another docker container on the same host with published port ie. 8888:80 3. login with desktop peer@latest to self-hosted netbird@latest and try to reach container on the linux docker peer with published port **Expected behavior** Behaviour expected like with netbirdio/netbird:0.31.0, containers with published ports can be reached here. Starting from 0.32.0 this is not possible anymore. **Are you using NetBird Cloud?** self-host NetBird **NetBird version** `latest`, ie. 0.38.0 **Is any other VPN software installed?** no **Debug output** To help us resolve the problem, please attach the following debug output netbird status -dA -> unavailable for docker container peer As well as the file created by netbird debug for 1m -AS -> unavailable for docker container peer **Have you tried these troubleshooting steps?** - [x ] Checked for newer NetBird versions - [x ] Searched for similar issues on GitHub (including closed ones) - [x ] Restarted the NetBird client - [x ] Disabled other VPN software - [x ] Checked firewall settings
saavagebueno added the triage-needed label 2026-08-05 01:12:23 -04:00
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#7301