FAQ

Short answers, each with the page that has the detail.

Do I need Portainer?

No. A host with no manager in its config runs stacks from their folders with Compose. seawall init --manager portainer picks Portainer and writes [manager] default = "portainer". The commands are the same either way. [manager] in the config can set it per stack. stack migrate moves a running stack between the two.

Can I use it on a host that already runs stacks?

Yes. Each init step checks first and leaves what it finds in place. Compose projects in the stacks folder are taken on as they are. See Who runs a stack. stack find lists stacks outside the stacks folder. stack move brings one in.

Does it update stacks on its own?

Only when you set a level. [updates.auto] is off by default. With a level set, the nightly window takes updates through stack update's backup, deploy and rollback. Without one, the daily check reports updates and the CVEs they fix, and you take each one yourself. seawall updates plan shows the next run. See Updates.

Does it manage several hosts?

No. One seawall runs one host. Install it on each host.

Does it work offline?

Mostly. Stacks, alerts, facts and backups work on the host alone. The wizard's search, the image check and release notes need the registries. Offline you type the image in full. Security lists every outside connection.

How do I undo a change?

Deploys and updates back up what ran. stack rollback <stack> --yes deploys the version before. seawall audit lists every change seawall made.

Can I use it in scripts?

Yes. Off a terminal init asks no questions. Pass --yes to act. The wizard needs a terminal. Write a compose file yourself and run stack new instead. Use the global --check to get exit code 1 when a report finds something. Severe changes need --confirm <name> without a terminal. seawall status --json prints the status as JSON.