# FAQ

**Q: Does this replace Docker on Unraid?**
Not initially. Phase 1 runs Podman alongside Docker with fully separate storage,
networking, and firewall rules. A later phase adds an option to disable Docker
once feature parity is reached — see [ROADMAP.md](ROADMAP.md).

**Q: Is this rootless or rootful Podman?**
Phase 1 is rootful only, matching Docker's current trust model on Unraid.
Rootless is planned for a later phase — see
[ARCHITECTURE.md](ARCHITECTURE.md#0-ziele--nicht-ziele).

**Q: Will my existing Docker containers/appdata work with Podman?**
Bind-mounted appdata under `/mnt/user/appdata/...` can generally be reused, but
there is no automatic Docker→Podman template migration in Phase 1. See
[ARCHITECTURE.md, section 9 (Volumes)](ARCHITECTURE.md#9-volumes).

**Q: Why isn't there a WebUI yet?**
The MVP intentionally ships CLI-only to validate the persistence, packaging, and
init model first, before investing in GUI work. See
[ARCHITECTURE.md, section 18](ARCHITECTURE.md#18-zukünftige-webui).

**Q: Why does this need a cache pool / dedicated disk instead of just using
`/mnt/user`?**
Podman's `overlay` storage driver needs real filesystem semantics that the
`/mnt/user` FUSE layer (`shfs`) doesn't reliably provide. See
[ARCHITECTURE.md, section 4.3](ARCHITECTURE.md#43-persistente-nutzdaten-cache-pool-bevorzugt-array-als-fallback).

**Q: Is this affiliated with Unraid, Inc. or the Podman project?**
No. This is an independent, community-driven plugin project.