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

Required.

Options

--to <TO>

The owner's rootless runtime it goes to (without it, a move that stopped part way is finished or rolled back)

One of docker-rootless, podman-rootless.

--confirm <NAME>

The stack's name, to move one with bind folders without a terminal (--yes alone asks for it to be typed)

--clean

Remove what the runtime it left still holds of it: root's after a move, the owner's after a move back

--back

Bring 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

Default 15m.

--yes

Carry out the plan (without it, this is a dry run)

--wait

After a redeploy, wait out the 2-minute compare with before. Without it the facts timer runs it (SeawallDeployWorse)

Every command also takes the global options.

Examples

seawall stack runtime ghost --to podman-rootless
seawall stack runtime ghost --back