seawall stack runtime
Move a running stack to the rootless owner's runtime, with its data.
Move a running stack to the rootless owner's runtime, with its data
A dry run first: what can't move, the data and its size, the routes NPM switches to a port on the ingress network's gateway, and the second compose file it runs with.
Usage
seawall stack runtime [OPTIONS] <STACK>
Changes the host
Without --yes it prints the plan and changes nothing.
Arguments
<STACK>The stack, by Portainer name or directory
Options
--to <TO>The owner's rootless runtime it goes to (without it, a move that stopped part way is finished or rolled back)
--confirm <NAME>The stack's name, to move one with bind folders without a terminal (
--yesalone asks for it to be typed)--cleanRemove what the runtime it left still holds of it: root's after a move, the owner's after a move back
--backBring a moved stack back to root's runtime, its data copied from what ran since
--silence <SILENCE>How long to silence its container alerts for the move; 0 for none
--yesCarry out the plan (without it, this is a dry run)
--waitAfter a redeploy, wait out the 2-minute compare with before. Without it the facts timer runs it (
SeawallDeployWorse)
Examples
seawall stack runtime ghost --to podman-rootless
seawall stack runtime ghost --back