Redash on Windows With Docker

I am trying to install redash on windows (8.1) machine. I am using docker-toolbox.

I am referring to redash.docker.windows.setup.md · GitHub

I am getting following error at step “docker build .”

<— Last few GCs —>

[97:0x42a4e20] 208483 ms: Mark-sweep 986.6 (999.0) → 985.2 (999.0) MB, 1300.5 / 0.0 ms (average mu = 0.104, current mu = 0.005) allocat
on failure scavenge might not succeed
[97:0x42a4e20] 209786 ms: Mark-sweep 986.6 (999.0) → 985.7 (998.5) MB, 1298.6 / 0.0 ms (average mu = 0.055, current mu = 0.003) allocat
on failure scavenge might not succeed

<— JS stacktrace —>

==== JS stack trace =========================================

0: ExitFrame [pc: 0x140de99]

Security context: 0x22d1b75c08d1
1: /* anonymous /(aka / anonymous */) [0x1454e3d1f441] [/frontend/node_modules/terser-webpack-plugin/node_modules/webpack-sources/lib
applySourceMap.js:~58] [pc=0x38c032c9c094](this=0x393fe30804b1 ,0x080f5e7b9df1 <String[2]: r=>,0x31a23f6aa931 )
2: SourceNode_walk [0x1cc14e4037f1] [/frontend/node_modules/source-ma…

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
1: 0xa1a640 node::Abort() [node]
2: 0xa1aa4c node::OnFatalError(char const*, char const*) [node]
3: 0xb9a68e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [node]
4: 0xb9aa09 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [node]
5: 0xd57c85 [node]
6: 0xd58316 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [node]
7: 0xd64bd5 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [node]
8: 0xd65a85 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags)
node]
9: 0xd6853c v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal
:AllocationAlignment) [node]
10: 0xd2ef5b v8::internal::factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [node]
11: 0x107158e v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
12: 0x140de99 [node]
Aborted (core dumped)
npm ERR! code ELIFECYCLE
npm ERR! errno 134
npm ERR! redash-client@9.0.0-beta build: npm run clean && npm run build:viz && NODE_ENV=production webpack
npm ERR! Exit status 134
npm ERR!
npm ERR! Failed at the redash-client@9.0.0-beta build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /frontend/.npm/_logs/2021-06-04T10_28_08_323Z-debug.log
The command ‘/bin/sh -c if [ “x$skip_frontend_build” = “x” ] ; then npm run build; else mkdir -p /frontend/client/dist && touch /frontend/c
ient/dist/multi_org.html && touch /frontend/client/dist/index.html; fi’ returned a non-zero code: 134