Module switch 

Moving from one container engine to the other: what the new engine lacks, what of the old one QCode carries over, and what it leaves behind.

The two engines keep separate stores. A profile image built with docker is not in podman, and a workspace’s home volume — the harness’s settings, history and login — made in podman is not in docker. Nothing here moves anything: it copies. The old engine keeps every volume it had, so the person can switch back and find everything as it was; removing what is left there is the person’s own choice, and only containers are ever offered for removal.

Everything here runs engine commands and waits for them, so it belongs on a background thread.

Structs

Carried

A volume of the old engine that a switch can carry over.

Leftover

The containers QCode made that are still in the old engine.

Survey

What a switch finds: what the new engine lacks and what the old one holds.

Functions

carried

Whether the volume name is one QCode carries from one engine to the other.

copy

Copies the volume name from old into new, as user.

offer_at_start

The engine to offer at start, when the saved one does not answer and the other one does.

other

The engine that is not kind.

remove

Removes QCode’s containers from old. Only containers: every volume stays, so switching back finds every home and login where it was.

survey

Asks both engines what a switch from old to new involves for profiles.

Type Aliases

Unmoved

Why a volume could not be copied, in words the person is shown as they are.