Check Docker Architecture to Avoid Manifest Errors

[AgentBurgundy]

Currently, if someone is using Docker for Windows and is currently setup using Windows containers, they will receive this error.

(node:6320) UnhandledPromiseRejectionWarning: Error: (HTTP code 404) no such container - No such image: node:latest
    at D:\Git\try\node_modules\docker-modem\lib\modem.js:254:17
    at getCause (D:\Git\try\node_modules\docker-modem\lib\modem.js:284:7)
    at Modem.buildPayload (D:\Git\try\node_modules\docker-modem\lib\modem.js:253:5)
    at IncomingMessage.<anonymous> (D:\Git\try\node_modules\docker-modem\lib\modem.js:229:14)
    at IncomingMessage.emit (events.js:187:15)
    at endReadableNT (_stream_readable.js:1098:12)
    at process.internalTickCallback (internal/process/next_tick.js:72:19)
(node:6320) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:6320) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

We could probably make this easier to the end user by checking the current architecture using the command docker info -f '{{.OSType}}/{{.Architecture}}' as defined in this article and either throwing an error or even attempting to switch over the architecture auto-magically.

[BrunnerLivio]

Sounds great! Though I am in holidays for the next two weeks, so won’t be able to look further into anytime soon. But I think we should try to switch to the needed architecture automagically!