truenas-docker-ops

Included with Lifetime

$97 forever

Playbook for anything on the TrueNAS host — consult before touching services, data, or containers. Covers SSH entry, container interaction, and data/layout notes so you can operate safely on TrueNAS.

Cloud & DevOpsscripts

What this skill does


# TrueNAS Docker Operations

## Essentials

- Connect: `ssh truenas` (auth pre-configured)
- Stacks managed via Ansible in `ansiblonomicon` repo folder (in `ansible/stacks/`)
- Deployed compose files: `/mnt/performance/docker/stacks/<stack>/compose.yaml`
- Container configs: `/mnt/performance/docker/<stack>/`
- Large media data: `/mnt/capacity/watch/<container>/`
- Network/IP assignments: see individual compose files or `ansible/inventory/group_vars/truenas.yml` in ansiblonomicon

## Common Commands

| Task              | Command                                                               |
| ----------------- | --------------------------------------------------------------------- |
| List containers   | `ssh truenas docker ps`                                               |
| Filter containers | `ssh truenas docker ps \| grep <name>`                                |
| View compose      | `ssh truenas cat /mnt/performance/docker/stacks/<stack>/compose.yaml` |
| View logs         | `ssh truenas docker logs <container>`                                 |
| Exec command      | `ssh truenas docker exec -i <container> <command>`                    |
| Inspect           | `ssh truenas docker inspect <container>`                              |

## Deployment

Stacks are deployed via Ansible, not manually:

```bash
# From ansiblonomicon repo
poe truenas           # Full playbook
poe truenas -t stacks # Just stacks
```

but you can run ad-hoc commands against the docker containers/compose files on the truenas host. Changes will not be preserved unless they are made to the ansiblonomicon repo.

## Anypod Data Layout

- Host data root: `/mnt/capacity/watch/anypod/data` (binds to `/data` in container)
  - Media downloads: `media/<feed_id>/`
  - Transcripts: `transcripts/<feed_id>/`
  - DB: `/data/db/anypod.db`
- DB tables (anypod.db):
  - `feed` (PK `id`; feed metadata, source info, timestamps, counters)
  - `download` (PK `feed_id`, `id`; per-episode info, status, transcript fields)
  - `appstate` (PK `id`; `last_yt_dlp_update`, other global state)

## Helper Scripts

### Python (handles nested heredoc/quoting)

`scripts/docker_exec_python.sh <container> '<python_code>'`

```bash
scripts/docker_exec_python.sh anypod '
import sqlite3, json
conn = sqlite3.connect("/data/db/anypod.db")
conn.row_factory = sqlite3.Row
rows = conn.execute("SELECT * FROM feed").fetchall()
print(json.dumps([dict(r) for r in rows], indent=2))
conn.close()
'
```

> **Note**: Default interpreter is `/app/.venv/bin/python` (works for anypod). Override with `CONTAINER_PYTHON`:
>
> ```bash
> CONTAINER_PYTHON=/usr/bin/python3 scripts/docker_exec_python.sh your-container 'print("hi")'
> ```

### SQLite

`scripts/docker_exec_sqlite.sh <container> <db_path> '<sql_query>'`

```bash
scripts/docker_exec_sqlite.sh anypod /data/db/anypod.db '
SELECT feed_id, status, COUNT(*) AS count
FROM download
GROUP BY feed_id, status;
'
```

## When to Use Scripts vs Direct

- **Scripts**: Multi-line Python/SQL, complex quoting
- **Direct `docker exec`**: Simple commands, logs, inspection

## Quick Examples

```bash
# Is anypod running?
ssh truenas docker ps | grep anypod

# View anypod compose
ssh truenas cat /mnt/performance/docker/stacks/anypod/compose.yaml

# Query anypod DB
scripts/docker_exec_sqlite.sh anypod /data/db/anypod.db "SELECT * FROM feed;"
```

Files: 3

Size: 5.8 KB

Complexity: 27/100

Category: Cloud & DevOps

Source: https://github.com/thurstonsand/thurstons-claude-skills/tree/main/homelab/skills/truenas-docker-ops

Related in Cloud & DevOps

appbuilder-action-scaffolder

Included

Create, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.

Cloud & DevOpsscripts

orchestrating-datacloud

Included

Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).

Cloud & DevOpsscripts

github-project-automation

Included

Automate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error

Cloud & DevOpsscripts

sf-datacloud

Included

Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).

Cloud & DevOpsscripts

fabric-cli

Included

Use this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.

Cloud & DevOpsscripts

lark

Included

Lark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.

Cloud & DevOpsscripts