Service is launched with TAR BALL artifacts. If a container is exited due to any reasons, container relaunch policy try to relaunch the container on same node with same container work space. As a result, container relaunch is keep on failing.
If container relaunch max-retry policy is disabled, then container never launched in any other nodes also rather it keep on retrying on same node manager which never succeeds.
There are two issues
- Container relaunch is keep on failing
- Log message is misleading