[BUG] <title>Container loses bridge network attachment after Ugreen UGOS system update
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 25/100
- Type d'issue
- Bug
- Clarté
- À clarifier
- Activité
- Active
- Stack technique
- docker
- Domaine
- devops, networking
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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
- Langage dominant
- Dockerfile
- Étoiles
- 152
- Forks
- 49
- Merge moyen
- 3 j 13 h
- PR mergées (30 j)
- 1
Préparer son environnement
- Fournit un Dockerfile ou un fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de linuxserver/docker-emby
-
[BUG] Loading HangsOuverteno-issue-activity
Difficulté 4/5 3-5 jours Accessibilité débutants 35/100
linuxserver/docker-emby#123 · 7 commentaires ·
Toutes les issues de linuxserver/docker-emby
Issues similaires
-
windows-artifacts: the win-arm64 job uses a Visual Studio generator missing from windows-11-armOuverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 86/100
-
Own-agent checks: reject the Actions bot id in admit.mjs and test the source label in pr-verifyOuverte
Difficulté 2/5 1-3 heures Accessibilité débutants 74/100
melodic-software/claude-code-plugins#17374 · 2 commentaires ·
Les mainteneurs répondent en général sous 1 jour
-
area: doc-engine area: infrastructure bug community-request
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
snapotter-hq/SnapOtter#4834 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 73/100
soroswap/token-list#125 ·
Les mainteneurs répondent en général sous 1 jour