minor cleanups
This commit is contained in:
@@ -67,9 +67,9 @@ Within Docker, qBittorrent faces problems like:
|
||||
| Inconsistent paths | Container paths differ from host paths |
|
||||
| Poor integration | Radarr/Sonarr struggles with Docker paths |
|
||||
|
||||
### Conclusion:
|
||||
**Conclusion:**
|
||||
|
||||
Running qBittorrent directly on the host is faster, more reliable, and simpler.
|
||||
- Running qBittorrent directly on the host is faster, more reliable, and simpler.
|
||||
|
||||
---
|
||||
|
||||
@@ -84,9 +84,9 @@ Plex relies on:
|
||||
| Network discovery (multicast/IGMP) | Blocked or isolated inside containers |
|
||||
| Handling millions of metadata files | Poor container filesystem performance |
|
||||
|
||||
### Conclusion:
|
||||
**Conclusion:**
|
||||
|
||||
Plex runs best on the host machine for speed, compatibility, and stable transcoding.
|
||||
- Plex runs best on the host machine for speed, compatibility, and stable transcoding.
|
||||
|
||||
---
|
||||
|
||||
@@ -152,7 +152,7 @@ Once rebooted, your system will be ready to run containerized ARR services.
|
||||
|
||||
---
|
||||
|
||||
## 🚀 Next Step: Install Plex on the Host
|
||||
## ➡️ Next Step: Install Plex on the Host
|
||||
|
||||
Once Docker is installed, move on to installing Plex directly on the host to ensure your server is ready to stream media
|
||||
as the ARR stack populates your libraries.
|
||||
|
||||
Reference in New Issue
Block a user