Calling build inside a docker container

[klawitterb]

Currently playing a bit around with the buildservice and gitlab runners.
When I call the cloudron build command using the build service it fails with the following error:

Pushing 7961033aba9e [==================================================>]     512B/usr/local/node-18.12.1/lib/node_modules/cloudron/src/build-actions.js:100
                process.stdout.clearLine();
                               ^
TypeError: process.stdout.clearLine is not a function
    at EventSource.<anonymous> (/usr/local/node-18.12.1/lib/node_modules/cloudron/src/build-actions.js:100:32)
    at EventSource.emit (node:events:513:28)
    at _emit (/usr/local/node-18.12.1/lib/node_modules/cloudron/node_modules/eventsource/lib/eventsource.js:287:17)
    at parseEventStreamLine (/usr/local/node-18.12.1/lib/node_modules/cloudron/node_modules/eventsource/lib/eventsource.js:302:9)
    at IncomingMessage.<anonymous> (/usr/local/node-18.12.1/lib/node_modules/cloudron/node_modules/eventsource/lib/eventsource.js:259:11)
    at IncomingMessage.emit (node:events:513:28)
    at addChunk (node:internal/streams/readable:324:12)
    at readableAddChunk (node:internal/streams/readable:297:9)
    at Readable.push (node:internal/streams/readable:234:10)
    at HTTPParser.parserOnBody (node:_http_common:129:24)

Any ideas? Works perfectly fine on my local machine. My gitlab runner is running inside a docker container as well, might it be related?

[girish]

@klawitterb said in Calling build inside a docker container:

process.stdout.clearLine is not a function

Oh, this seems like we need to handle a case where stdout is not stdout (like the CI).

[girish]

Right, I can reproduce this with a simple program:

$ node -e 'process.stdout.clearLine();'
$ node -e 'process.stdout.clearLine();' >/dev/null
[eval]:1
process.stdout.clearLine();
               ^

TypeError: process.stdout.clearLine is not a function
    at [eval]:1:16
    at Script.runInThisContext (node:vm:129:12)
    at Object.runInThisContext (node:vm:307:38)
    at node:internal/process/execution:79:19
    at [eval]-wrapper:6:22
    at evalScript (node:internal/process/execution:78:60)
    at node:internal/main/eval_string:28:3

Node.js v18.16.0

[girish]

@klawitterb I published a new version. Can you try with CLI v5.3.4 ?

[klawitterb]

@girish works perfectly fine now, thanks for the quick fix