"uv_os_get_passwd" error during an Octane build in a docker image

I'm running a build in a docker image and am getting the following error which is killing the build process:

```
$ ember build -e=development
A system error occurred: uv_os_get_passwd returned ENOENT (no such file or directory)
(node:140) UnhandledPromiseRejectionWarning: SystemError [ERR_SYSTEM_ERROR]: A system error occurred: uv_os_get_passwd returned ENOENT (no such file or directory)
at Object.userInfo (os.js:249:11)
at summarizeProcess (/tmp/digitalization/teambuilder-frontend/node_modules/console-ui/lib/summarize-process.js:17:15)
at writeError (/tmp/digitalization/teambuilder-frontend/node_modules/console-ui/lib/write-error.js:114:3)
at UI.writeError (/tmp/digitalization/teambuilder-frontend/node_modules/console-ui/lib/index.js:167:20)
at CLI.logError (/tmp/digitalization/teambuilder-frontend/node_modules/ember-cli/lib/cli/cli.js:318:13)
at CLI.run (/tmp/digitalization/teambuilder-frontend/node_modules/ember-cli/lib/cli/cli.js:253:12)
at process._tickCallback (internal/process/next_tick.js:68:7)
at Function.Module.runMain (internal/modules/cjs/loader.js:834:11)
at startup (internal/bootstrap/node.js:283:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
(node:140) 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:140) [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.
```

Anyone solved this yet? If so, what was the solution?

Reproduziere den Fehler mit `ember build -e=development` im Docker-Image und lies anschließend die Einstiegspunkte des Stack-Traces in `console-ui/lib/summarize-process.js` und `console-ui/lib/write-error.js`. Prüfe, wie der Fehler von `os.userInfo` während der Fehlerberichterstattung behandelt wird; fertig ist die Aufgabe, wenn der Build nicht mehr mit diesem Fehler beendet wird und der Fehlerpfad weiterhin nutzbar ist.

Vom Indexierungsmodell aus dem Issue-Text verfasst.