A ZimaOS Legacy App tile can represent a Docker container that was not installed through the normal App Store registration path. The unfamiliar name admiring_swanson is therefore not enough to identify what the container actually does.
Identify the Container Before Importing or Deleting It
The correct first command from the thread was:
docker ps -aDocker's Docker container listing confirms that docker ps -a lists containers in all states and exposes fields such as image, status, and names. The image name is normally more useful than a randomly generated container name.
Legacy App Does Not Mean Malware
A Legacy App tile means the dashboard found a container it can offer to import/manage; it does not by itself establish who created the container or whether it is malicious. Inspect the image, creation time, mounts, ports, labels, and command before making that judgment.
The first Docker app explains the normal ZimaOS Docker lifecycle, while ZimaOS App Store requirements helps distinguish an App Store-managed package from a container created outside that registration flow.
Remove Only the Container You Have Identified
After the user identified the unwanted container, stopping and removing it cleared the Legacy App. Docker's Docker container removal documents container removal and also warns that volume behavior depends on how storage was attached.
If you want a GUI for inspecting Docker stacks rather than raw commands, the Portainer on ZimaOS provides a current ZimaOS management path.
Do Not Copy a Container ID from Someone Else
Container IDs are unique to each host. Use your own docker ps -a output, identify the exact image and container, and only then stop or remove it. If the container is tied to important persistent data, back up that data before deletion.
Bottom Line
An unexplained Legacy App should be treated as an unknown Docker container, not immediately imported or deleted. Inspect it first with Docker, determine whether it belongs to software you recognize, then remove only the confirmed unwanted container. In the source case, removing that container cleared the dashboard tile.
