调试

运维部署 社区

技能解读

当前原文的自动摘译,尚未人工审校。

关键日志位置

日志 · 位置 · 用途 应用程序日志 · logs/nano-core.log · 路由器、调度程序、运行时编排 应用程序错误日志 · logs/nano-core.error.log · 主机进程故障 运行时运行日志 · groups/<folder>/logs/runtime-*.log · 每次运行的 stdout/stderr、挂载、环境诊断

4)主机模式门控(高级)

主机模式需要: CONTAINER_RUNTIME=host FFT_NANO_ALLOW_HOST_RUNTIME=1 生产主机模式还需要: FFT_NANO_ALLOW_HOST_RUNTIME_IN_PROD=1

“无效的容器运行时”

原因:.env包含不支持的值。修复:

“找不到支持的运行时”

原因:Docker 不可用且主机模式未明确允许。修复选项:启动 Docker 桌面/Docker 守护进程。或者在.env中显式启用主机模式:

运行时退出并显示代码 1

检查最新的运行时日志:然后验证凭据:

流狐档案 运行与权限由流狐静态检查推断,不代表作者声明或实际测试结果。
领域
运维部署
作者声明的智能体
未找到明确声明;不据此推断已兼容或已测试
静态检查
88 / 100 · 启发式扫描,不代表运行安全
运行环境证据
未执行;当前没有隔离运行测试证据
作者 / 版本 / 许可证
@0-CYBERDYNE-SYSTEMS-0 · 未声明许可证
上下文用量评级
低消耗
接入复杂程度
需手动接入
是否需要外部接口密钥
需要 · Anthropic
兼容的系统
Docker
运行环境要求
Node.js · Docker
检测到的文件与系统行为
  • 只读
  • 命令执行
  • 读取环境变量
网络行为
允许外网请求
安装命令数
无(仅作为资料)

需要注意: 未声明工具权限范围;实际权限由运行环境决定。

作者说明文件(原文) SKILL.md

# nano-core Runtime Debugging

This guide covers host-side diagnosis for current runtime modes:
- Docker (default)
- Host runtime (advanced, explicit opt-in)

## Runtime Architecture

```
Host process (src/index.ts)
  -> runtime selection (src/container-runtime.ts)
  -> agent execution (src/container-runner.ts)
     - Docker mode: docker run nano-core-agent:latest
     - Host mode: node container/agent-runner/dist/index.js
```

## Key Log Locations

| Log | Location | Purpose |
|---|---|---|
| App log | `logs/nano-core.log` | Router, scheduler, runtime orchestration |
| App error log | `logs/nano-core.error.log` | Host process failures |
| Runtime run log | `groups/<folder>/logs/runtime-*.log` | Per-run stdout/stderr, mounts, env diagnostics |

## Quick Health Checks

### 1) App build/runtime sanity

```bash
npm run typecheck
npm run build
```

### 2) Runtime mode resolution

```bash
node -e "import('./dist/container-runtime.js').then(m=>console.log(m.getContainerRuntime()))"
```

### 3) Docker availability (default)

```bash
docker --version
docker info >/dev/null && echo "Docker OK" || echo "Docker NOT running"
```

### 4) Host mode gating (advanced)

```bash
grep -E '^(CONTAINER_RUNTIME|FFT_NANO_ALLOW_HOST_RUNTIME|FFT_NANO_ALLOW_HOST_RUNTIME_IN_PROD)=' .env || true
```

Host mode requires:
- `CONTAINER_RUNTIME=host`
- `FFT_NANO_ALLOW_HOST_RUNTIME=1`

Production host mode additionally requires:
- `FFT_NANO_ALLOW_HOST_RUNTIME_IN_PROD=1`

## Common Failure Modes

### "Invalid CONTAINER_RUNTIME"

Cause: `.env` contains an unsupported value.

Fix:
```bash
sed -i.bak 's/^CONTAINER_RUNTIME=.*/CONTAINER_RUNTIME=auto/' .env
```

### "No supported runtime found"

Cause: Docker unavailable and host mode not explicitly allowed.

Fix options:
1. Start Docker Desktop / Docker daemon.
2. Or explicitly enable host mode in `.env`:
```bash
CONTAINER_RUNTIME=host
FFT_NANO_ALLOW_HOST_RUNTIME=1
```

### Runtime exits with code 1

Check newest runtime log:
```bash
ls -t groups/*/logs/runtime-*.log | head -1 | xargs -I{} sh -lc 'echo "== {} =="; tail -120 "{}"'
```

Then validate credentials:
```bash
grep -E '^(CLAUDE_CODE_OAUTH_TOKEN|ANTHROPIC_API_KEY|PI_API|PI_MODEL|ZAI_API_KEY)=' .env
```

### Session resumption problems

Verify per-group session mount path exists:
```bash
ls -la data/pi/main/.pi 2>/dev/null || true
```

Ensure runtime logs show expected mounted session directory and no permission errors.

## Manual Runtime Smoke Tests

### Docker mode smoke

```bash
echo '{}' | docker run -i --entrypoint /bin/echo nano-core-agent:latest "Container OK"
```

### Host mode smoke

```bash
npm --prefix container/agent-runner run build
CONTAINER_RUNTIME=host FFT_NANO_ALLOW_HOST_RUNTIME=1 FFT_NANO_DRY_RUN=1 npm run dev
```

## Service-level Checks (launchd)

```bash
launchctl list | grep nano-core || true
launchctl kickstart -k gui/$(id -u)/com.nano-core
sleep 2
tail -80 logs/nano-core.log
```

## One-Pass Diagnostics Script

```bash
echo "1) Node/build"
node --version
npm run -s build >/dev/null && echo "build OK" || echo "build FAIL"

echo "\n2) Docker"
docker info >/dev/null 2>&1 && echo "docker OK" || echo "docker NOT ready"

echo "\n3) Runtime policy"
grep -E '^(CONTAINER_RUNTIME|FFT_NANO_ALLOW_HOST_RUNTIME|FFT_NANO_ALLOW_HOST_RUNTIME_IN_PROD)=' .env || echo "no runtime env overrides"

echo "\n4) Latest runtime logs"
ls -t groups/*/logs/runtime-*.log 2>/dev/null | head -3 || echo "no runtime logs yet"
```

## Escalation Data to Capture

If issue persists, capture and share:
1. `logs/nano-core.log` tail (last 120 lines)
2. Latest `groups/<folder>/logs/runtime-*.log`
3. Output of `docker info` (or host mode env flags)
4. Current `.env` runtime keys (redact secrets)

讨论

基于 GitHub Discussions。登录 GitHub 即可参与讨论、点赞、订阅更新。