Cablebag 0.19 and 0.20: Containers, stacks, templates and moving stacks between servers

[maferick]

Cablebag 0.20.0 is out. Cablebag updates itself: the status line shows Update to 0.20.0, one click installs it. The installer is also on the release page.

Containers, a bit like Portainer but inside Cablebag

Right-click an SSH session (or an open SSH tab) and choose Containers. Docker is asked over the SSH login you already have; no Docker port is opened anywhere.

• A short list of every container on the server. Only what is wrong stands out: unhealthy, restarting, 23 restarts. Needs a look and Stopped show just those.
• Pick a container for its details: image, web ports to open in a tab, its project and compose file, and Logs, Shell, Restart and Stop.
• Where was that compose file again? Docker remembers it for every container started with Compose, and Cablebag shows it. Edit it in Cablebag's editor (you see the changes before anything is written), then Apply the compose file.
• Stacks made in Portainer are marked; their file is shown read-only, so you keep changing them in Portainer.

Stacks and templates (0.20)

• New stack puts a compose file (and an optional .env) in ~/stacks/<name> on the server and starts it. Stacks without containers show under Not running, ready to start again.
• Templates: a compose file with blanks such as {{port}} or {{password}}, asked when you use it. Save any running project as a template, also a container that was started without Compose (Cablebag writes the compose file for it). Values that look like passwords, tokens or keys become blanks, so a template never holds a secret. Templates go along with Sync.

Move a stack to another server (0.20)

Check the move first: Cablebag finds where every folder the stack uses is on the other server, and names what cannot move by itself (data only on this server), ports already in use, missing networks, a different processor, and registries the other server is not logged in to. Images are pinned to the exact version running now. Then Move stops it here, starts it there and waits until it is healthy. When it does not come up healthy, Cablebag goes back by itself. Every move is kept in a list.

And

• Ask the assistant about a container: it starts with the state and the last log lines, and the button already asks the right question ("Why does it keep restarting?").
• Docker through sudo with your password, on servers where your login may not use Docker directly; asked once per tab.
• A Proxmox server can be removed from its menu in the session tree.

Where to read more

• Containers
• What's new, the full list

Ideas, or something that does not work on your servers? Say so here or with Report a problem in Cablebag.