[BUG] <title>Container loses bridge network attachment after Ugreen UGOS system update

Offen
#124 2 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
25/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
docker
Bereich
devops, networking

Rechercherichtung

Start with the UGOS Docker GUI configuration and compare the working and broken startup logs, especially eth0 versus lo and the two recorded kernel versions. Reproduce the failure across an update if possible; done means identifying an image-side workaround or documenting that the failure is outside linuxserver/emby and cannot be fixed here.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

no-issue-activity
Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

On a Ugreen NASync DXP480T Plus running UGOS Pro, every system update breaks the container's network attachment. After an update, the container starts and reports as Running, but the NetworkManager only detects the loopback address (127.0.0.1 and ::1) — the bridge address (172.x.x.x) is missing entirely. The container is then unreachable from the network.

The log signature is:
Detected local ip addresses: [{"IPAddress":"127.0.0.1"...},{"IPAddress":"::1"...}]
— with no 172.x address present.

The fix is to delete and recreate the container. This has occurred across at least three separate UGOS updates.

This is likely a UGOS issue rather than an image issue, but documenting it here in case a workaround is possible from the image side (e.g. a restart policy or network health check).

Expected Behavior

No response

Steps To Reproduce
  1. Run linuxserver/emby container in bridge mode on a Ugreen NASync DXP480T Plus NAS (UGOS Pro)
  2. Perform a UGOS system update
  3. After the update, the container restarts automatically
  4. Attempt to access Emby on port 8096 — connection refused
Environment
OS: UGOS Pro (Debian 12 based), kernel updated by NAS firmware
How docker service was installed: Built into UGOS Pro (Ugreen's Docker app)- OS:
- How docker service was installed:
CPU architecture

x86-64

Docker creation
For **Docker creation**, paste this:


Created via Ugreen UGOS Pro Docker GUI (no CLI access). Settings:

Image: linuxserver/emby:latest
Network mode: bridge
Ports: 8096:8096/TCP, 8920:8920/TCP, 7359:7359/UDP, 1900:1900/UDP
Volumes:
  - Shared Folder/docker/emby/config → /config (Read/Write)
  - Shared Folder/media → /mnt/media (Read/Write)

Note: Container is created via the UGOS web GUI, not docker CLI or compose.
Container logs
# First occurrence (2026-09-19) — container working correctly after previous fix:
Info NetworkManager: Detected local ip addresses: [{"IPAddress":"172.17.0.3","HasGateWayAddress":true,...},{"IPAddress":"127.0.0.1",...},{"IPAddress":"::1",...}]

# Latest occurrence (2026-09-29) — after UGOS system update, broken state:
Info NetworkManager: networkInterface: Loopback lo, Speed: -1, Description: lo
Info NetworkManager: UnicastAddresses: 127.0.0.1,::1
Info NetworkManager: Detected local ip addresses: [{"IPAddress":"127.0.0.1","HasGateWayAddress":false,...},{"IPAddress":"::1",...}]

# Note: eth0 interface is entirely absent from network detection after the update.
# On working startups, eth0 is detected with GatewayAddress 172.17.0.1 and UnicastAddress 172.17.0.3.
# On broken startups, only the loopback interface (lo) is detected — eth0 is missing.
# The container shows as Running with correct port mappings, but is unreachable externally.
# Fix: delete and recreate the container. Restart does not fix it.

# UGOS kernel before update: #696c5cd7dce5
# UGOS kernel after update:  #f586cf5b8315
Vorherrschende Sprache
Dockerfile
Sterne
152
Forks
49
Ø Merge
3 T. 13 Std.
Gemergte PRs (30 T.)
1

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus linuxserver/docker-emby

Alle Issues in linuxserver/docker-emby

Ähnliche Issues

Weitere Issues zu DevOps

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.