[BUG] <title>Container loses bridge network attachment after Ugreen UGOS system update
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
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
- Run linuxserver/emby container in bridge mode on a Ugreen NASync DXP480T Plus NAS (UGOS Pro)
- Perform a UGOS system update
- After the update, the container restarts automatically
- 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
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Hat eine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus linuxserver/docker-emby
-
[BUG] Loading HangsOffenno-issue-activity
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 35/100
linuxserver/docker-emby#123 · 7 Kommentare ·
Alle Issues in linuxserver/docker-emby
Ähnliche Issues
-
windows-artifacts: the win-arm64 job uses a Visual Studio generator missing from windows-11-armOffen
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 86/100
-
Own-agent checks: reject the Actions bot id in admit.mjs and test the source label in pr-verifyOffen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
melodic-software/claude-code-plugins#17374 · 2 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
area: doc-engine area: infrastructure bug community-request
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
snapotter-hq/SnapOtter#4834 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 73/100
soroswap/token-list#125 ·
Maintainer antworten meist innerhalb von 1 Tag