# Troubleshooting (draft)

> Placeholder. Will be filled in as real failure modes are observed post-MVP.
> Cross-reference [ARCHITECTURE.md, section 16 (Fehlerbehandlung)](ARCHITECTURE.md#16-fehlerbehandlung)
> for the error-handling design these entries should map to.

## How to gather diagnostics

```sh
rc.podman status
podman info
podman system df
```

Relevant log locations:

- Container logs: `/mnt/*/system/podman/logs/containers/`
- Service log: `/mnt/*/system/podman/logs/podman-service.log`
- Unraid System Log: `Tools → System Log` in the WebUI

Please redact registry credentials/tokens before sharing logs in an issue.

## Known problem categories (to be populated)

### Storage

- `podman.img` full / near-full
- Loopback mount failures after unclean shutdown

### Networking

- Custom network / macvlan issues
- Conflicts with Docker's `iptables` chains

### Autostart

- Container stuck in a failed autostart loop

### Plugin update / rollback

- Config migration failures after an update