Messages seawall prints when something stops it. Each comes with what to run next.
First checks
seawall doctor # permissions, access to Docker, sudo, Portainer and Grafana
seawall status # what needs attention
seawall audit -n 20 # the last changes seawall made
init
Message
Do
is in the docker group, but this login started before that
Log out and back in. Then run seawall init --yes again. Steps already done show ✓.
SEAWALL_PORTAINER_PASSWORD must be 12 characters or more
Use a longer password, or leave the variable unset to type it.
A step fails
init stops at the first failure. Fix what it names and run it again. It carries on from that step.
Deploys and updates
Message
Do
X's disk copy differs from what's deployed: `seawall stack diff X` shows how
The container exits after it starts. Its logs say why.
killed X (it wouldn't stop)
The container ignored the stop signal for its grace period. With "Operation not permitted" in the lines it logged, its start script lacks KILL. Run stack harden X.
this change is severe: add --confirm X to make it without a terminal
A severe change needs a name typed as well as --yes. The plan says which. On a terminal you type it. In a script pass --confirm X.
the disk copy wasn't updated
The run was interrupted after Portainer took over. Run the stack reconcile it names.
X builds app (build:). Portainer can't build from its copy.