graceful exit in case the docker images are not found

[r3dsm0k3]

Currently, drogon exits with node errors while running init when the docker containers.

/home/fidel/.nvm/versions/node/v18.13.0/lib/node_modules/@icon-community/drogon/node_modules/docker-modem/lib/modem.js:336
      var msg = new Error(
                ^

Error: (HTTP code 404) no such container - No such image: iconcommunity/drogon:latest 
    at /home/fidel/.nvm/versions/node/v18.13.0/lib/node_modules/@icon-community/drogon/node_modules/docker-modem/lib/modem.js:336:17
    at getCause (/home/fidel/.nvm/versions/node/v18.13.0/lib/node_modules/@icon-community/drogon/node_modules/docker-modem/lib/modem.js:366:7)
    at Modem.buildPayload (/home/fidel/.nvm/versions/node/v18.13.0/lib/node_modules/@icon-community/drogon/node_modules/docker-modem/lib/modem.js:335:5)
    at IncomingMessage.<anonymous> (/home/fidel/.nvm/versions/node/v18.13.0/lib/node_modules/@icon-community/drogon/node_modules/docker-modem/lib/modem.js:303:16)
    at IncomingMessage.emit (node:events:525:35)
    at endReadableNT (node:internal/streams/readable:1359:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  reason: 'no such container',
  statusCode: 404,
  json: { message: 'No such image: iconcommunity/drogon:latest' }
}

Node.js v18.13.0

The error happens due to not having successfully completed the drogon install sub command (related : #21 ). In an ideal case, drogon should handle the error. When the docker container is not found, it should prompt to execute drogon install.