Migrating from Umbrel

Talome runs Umbrel apps natively. The Umbrel app store is one of Talome's built-in sources, and your existing Docker containers can be detected and managed without reinstallation. Your data stays in place.

What You Keep vs What You Gain

Step-by-Step Migration

1. Install Talome Alongside Umbrel

Talome and Umbrel use different ports. Install Talome without affecting your Umbrel setup:

curl -fsSL https://get.talome.dev | bash

Talome runs on ports 3000 (dashboard) and 4000 (API). Umbrel stays on port 80. No conflicts.

2. Discover Existing Containers

Open the Talome dashboard at http://your-server:3000 and ask:

"Show me all running Docker containers"

Talome displays every running container, including your Umbrel apps, with their names, images, ports, and health status.

3. Reinstall Apps via Talome

Talome v0.1 doesn't auto-import an existing Umbrel container into its management database — that feature is on the roadmap. The recommended path is to reinstall each app you want Talome to fully manage from Talome's app store, which includes the entire Umbrel catalog. Talome's Umbrel adapter strips Umbrel-specific quirks (the app_proxy sidecar, UMBREL_* env injection, platform hooks) automatically when it parses an Umbrel-format manifest.

"Stop the Umbrel Jellyfin container"
"Install Jellyfin from the Umbrel store"
"When you install it, mount /home/umbrel/umbrel/app-data/jellyfin/data/config to /config and the existing media directory to /media"

The Talome installer creates a fresh compose file in ~/.talome/app-data/jellyfin/, leaves your existing data on disk, and starts the new container. No data is copied or moved.

For containers you only want Talome to observe (read logs, check health, restart on crash), no reinstall is needed — list_containers, get_container_logs, and restart_container work on any container the Docker socket can see.

4. Notes on Umbrel-Specific Configuration

Umbrel apps include components that aren't needed under Talome. The Umbrel adapter handles these automatically when you install via the app store:

• app_proxy sidecar — stripped from the compose file. Talome has its own Caddy reverse proxy with auth.
• UMBREL_* environment variables — removed when the manifest is parsed. If an installed app actually depends on one (uncommon), Talome will surface it as an error after install; ask the AI to identify and replace it.
• Network configuration — Talome puts new apps on its own bridge network for container-to-container communication.

5. Configure Integrations

For apps with deep AI integration, add their connection details:

"Configure Sonarr — it's running at http://localhost:8989"
"Configure Jellyfin at http://localhost:8096"

The AI auto-discovers API keys when possible. Once configured, you unlock domain-specific tools — 27 arr tools for Sonarr/Radarr, 6 Jellyfin tools, 6 qBittorrent tools, and so on.

6. Verify Everything Works

"Check the health of all my apps"
"Diagnose all apps"

The AI runs healthchecks, verifies network connectivity between apps, and reports any issues.

7. Optional: Remove Umbrel

Once everything is managed by Talome:

# Stop the Umbrel management layer (keeps containers running)
sudo ~/umbrel/scripts/stop

Your containers continue running. Talome has taken over management. The Umbrel app store remains accessible through Talome's built-in Umbrel adapter.

Umbrel vs Talome

The Umbrel Adapter

Talome's umbrel-adapter syncs the full Umbrel app store into Talome's catalog:

1. Clones the Umbrel App Store repository
2. Parses each app's umbrel-app.yml manifest and docker-compose.yml
3. Strips Umbrel-specific fields (app_proxy definitions, UMBREL_* environment variable references, platform hooks)
4. Normalizes into Talome's manifest format (name, description, icon, category, ports, volumes, environment)
5. Makes apps available in the Talome store with an "Umbrel" source badge

The adapter handles Umbrel's unique patterns:

• app_proxy — Umbrel uses a reverse proxy sidecar per app. The adapter strips this from the compose file since Talome has its own Caddy-based proxy.
• UMBREL_DATA_DIR — Umbrel uses platform environment variables for paths. The adapter maps these to Talome's data directory structure.
• Tor integration — Umbrel's Tor-based remote access is not imported. Talome uses Tailscale instead.

Troubleshooting

Imported container not showing in app list

• Verify the container is running: "Is the Jellyfin container running?"
• Check Talome's managed app list: "List all managed apps"
• The container might need manual import if it has an unusual name

App errors after removing app_proxy

• Some Umbrel apps expect the proxy for path-based routing
• Check the app's logs: "Show me Jellyfin's logs"
• You may need to add a reverse proxy route: "Add a proxy route for Jellyfin"

Authentication issues

• Umbrel uses app_proxy for app-level auth. Without it, apps use their own authentication
• Make sure each app has its own credentials configured
• For apps without built-in auth, use Talome's reverse proxy with basic auth

UMBREL_ environment variables missing

• Check which variables the app needs: "Show me the environment variables for this app"
• Replace with Talome equivalents or hardcode the values
• Most apps work fine without Umbrel-specific variables

Network connectivity between apps

• Make sure apps are on the talome network: "List networks for Jellyfin"
• Connect if missing: "Connect Jellyfin to the talome network"
• Verify connectivity: "Test connectivity between Sonarr and qBittorrent"