Comment 2 for bug 1881150

This issue is another occurrence of: https://bugs.launchpad.net/starlingx/+bug/1877582

System was unlocked. Platform managed applications try to upload. The armada container attempts to start but fails. It is in an exited status but appears to be running after the reboot (likely due to a port conflict: bind: address already in use: unknown)

Key logs to confirm this is a dup are in daemon.log.4:
2020-05-28T10:04:04.935 controller-0 dockerd[83556]: info time="2020-05-28T10:04:04.935429681Z" level=error msg="e650bd9ec8d3e23c07a2b51b425b36b6ad5e27b685d5507abee5236577dbb5e8 cleanup: failed to delete container from containerd: no such container"
2020-05-28T10:04:04.957 controller-0 dockerd[83556]: info time="2020-05-28T10:04:04.957852906Z" level=error msg="Handler for POST /v1.35/containers/e650bd9ec8d3e23c07a2b51b425b36b6ad5e27b685d5507abee5236577dbb5e8/restart returned error: Cannot restart container e650bd9ec8d3e23c07a2b51b425b36b6ad5e27b685d5507abee5236577dbb5e8: task e650bd9ec8d3e23c07a2b51b425b36b6ad5e27b685d5507abee5236577dbb5e8 already exists: unknown"

The workaround for this is to run the following, then the apps will auto-upload/auto-apply
- docker rm <container> -- use id for armada container