Warn the users during the installation process that Application Updates remove unrelated containers from the system #7
Labels
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
Background
A user reported this after testing on a NVIDIA Jetson Orin, but the use case may also apply to anyone who has Docker pre-installed on their system.
After an Application Update,
docker system prune -a --force
is run (at least according to https://developer.toradex.com/torizon/torizon-platform/torizon-updates/torizon-updates-technical-overview/#identifying-unsuccessful-container-updates), and this removes all container images that are not actively used, whereas a reasonable expectation would be that Application Updates only touch the Docker resources it needs.Goal
Effectively warn users that Application Updates will remove Docker resources not referenced by the Docker Compose file of the Application Updates and explicitly ask them to acknowledge it:
The text was updated successfully, but these errors were encountered: