R60133 purge old ce dev image when updating pr devel

[nfawbert]

Tested on local VM stack;

1. Roll back to 1.1.17 VM snapshot
2. edit /opt/ce-dev/lib/commands/update.js with LOCAL "file:///home/fawbert/install.sh"
3. Create /home/fawbert/install.sh with;

echo "Killing deprecated running ce_dev_controller container..."
if [ "$(docker ps -q -f name=ce_dev_controller)" ]; then
    if [ "$(docker ps -aq -f status=running -f name=ce_dev_controller)" ]; then
        # cleanup
        docker kill ce_dev_controller
    fi
fi
echo "done."

3. sudo chmod 755 /home/fawbert/install.sh
4. ce-dev update
5. ce-dev create
6. cd projectname
7. ce-dev init
8. ce-dev start
9. ce-dev provision
10. ce-dev deploy

The solution will be implemented within 'install.sh' script;

ce-dev:install.sh;

echo "Killing deprecated running ce_dev_controller container..."
if [ "$(docker ps -q -f name=ce_dev_controller)" ]; then
    if [ "$(docker ps -aq -f status=running -f name=ce_dev_controller)" ]; then
        # cleanup
        docker kill ce_dev_controller
    fi
fi
echo "done."

During a 'ce-dev update', if the (old) controller container is found to be running, it is killed so that the new 'latest' tagged image is spun up on next run.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information