Troubleshooting Guide

Use this page to quickly locate common MANYOYO issues and run the shortest diagnostic path.

Quick Entry

• Build failures: build-errors
• Runtime failures: runtime-errors

Quick Reference

Symptom	Possible Cause	Quick Command	Details
manyoyo build fails	network/disk/permission	df -h, manyoyo build --iv 1.8.0-common	Build Issues
pinging container registry failed	local image not built	manyoyo build --iv 1.8.0-common	Image Pull Failures
permission denied	Docker/Podman permission issue	groups, docker ps	Permission Issues
env vars not effective	invalid envFile path/format	manyoyo config show --ef /abs/path/example.env	Env Var Issues

Minimal Diagnostic Flow

1. Basic checks

manyoyo -v
node --version
docker --version   # or podman --version

2. Inspect final config and command

manyoyo config show
manyoyo config command
manyoyo config show -r claude

3. Check images and containers

docker images | grep manyoyo   # or podman images
manyoyo ps

4. Verify env file loading (--ef only accepts absolute paths)

manyoyo config show --ef /abs/path/anthropic_claudecode.env
manyoyo run --ef /abs/path/anthropic_claudecode.env -x env | grep ANTHROPIC

Config Checks

• Run profiles are under runs.<name> in ~/.manyoyo/manyoyo.json.
• manyoyo run -r <name> reads runs.<name> from ~/.manyoyo/manyoyo.json.
• envFile must be an array of absolute paths.

Getting Help

1. Collect diagnostic info

uname -a
manyoyo -v
manyoyo config show
manyoyo ps

2. Export logs

manyoyo build --iv 1.8.0-common 2>&1 | tee build-error.log
docker logs <container-name> 2>&1 | tee runtime-error.log  # or podman logs

3. Submit an issue

• Repo: GitHub Issues
• Include: reproduction steps, logs, system info, and redacted config snippets.