[BUG] <title>Container loses bridge network attachment after Ugreen UGOS system update
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 25/100
- Tipo di issue
- Bug
- Chiarezza
- Da chiarire
- Stato di attività
- Attiva
- Stack tecnologico
- docker
- Ambito
- devops, networking
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Lingua principale
- Dockerfile
- Stelle
- 152
- Fork
- 49
- Merge medio
- 3g 13h
- PR unite (30g)
- 1
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di linuxserver/docker-emby
-
[BUG] Loading HangsApertano-issue-activity
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
linuxserver/docker-emby#123 · 7 commenti ·
Tutte le issue di linuxserver/docker-emby
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
soroswap/token-list#125 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
nekko-labs/nekko-agent#2998 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
francescopace/espectre#222 ·
I maintainer di solito rispondono entro 3 giorni
-
good first issue ops security
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
Kyvera-Labs/verixa#565 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno