Hi @berlin, I’m moving your question here so our devs can help you out!
i am experiencing problem with discovery init with ubuntu 18.04.
might this related to node version?
v10.13.0/lib/node_modules/@enigmampc/discovery-cli/node_modules/cli-color/trim.js:8
module.exports = function (str) { return str.replace(r, ‘’); };
^
TypeError: Cannot read property ‘replace’ of undefined
at module.exports (/home/berlion/.nvm/versions/node/v10.13.0/lib/node_modules/@enigmampc/discovery-cli/node_modules/cli-color/trim.js:8:46)
at Line.column (/home/berlion/.nvm/versions/node/v10.13.0/lib/node_modules/@enigmampc/discovery-cli/node_modules/clui/lib/clui.js:293:23)
at /home/berlion/.nvm/versions/node/v10.13.0/lib/node_modules/@enigmampc/discovery-cli/src/docker.js:45:14
at Array.forEach ()
at IncomingMessage.stream.on (/home/berlion/.nvm/versions/node/v10.13.0/lib/node_modules/@enigmampc/discovery-cli/src/docker.js:10:30)
at IncomingMessage.emit (events.js:182:13)
at IncomingMessage.EventEmitter.emit (domain.js:442:20)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at IncomingMessage.Readable.push (_stream_readable.js:219:10)
at HTTPParser.parserOnBody (_http_common.js:122:22)
at Socket.socketOnData (_http_client.js:441:20)
at Socket.emit (events.js:182:13)
at Socket.EventEmitter.emit (domain.js:442:20)
at addChunk (_stream_readable.js:283:12)
at readableAddChunk (_stream_readable.js:264:11)
at Socket.Readable.push (_stream_readable.js:219:10)
at Pipe.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
hi @berlin, can you tell which node version you’re running?
I used nvm to manage npm/node version, it’ll be better.
Before using nvm, I manually installed npm & node, it caused so many troubles.
Hey @adi could you check this out when you have a moment? @berlin – can you verify that this hasn’t been resolved yet? (and if it was, could you let us know how you fixed it?)
The latest versions of Node 10 and 11 should work fine. We recently updated our NodeJS repos from the latest 10 to the latest 11, and everything has been working fine for us on both.
Hey @berlin – was this resolved? I noticed you also had posted an issue with discovery test recently. Thanks for your patience as we try to figure this out.
@adi – can you take a look, and confirm which ubuntu version we’re supporting right now (or if it should matter)? I think the issue may be around Ubuntu version, though I am not sure why that would be at this time.
OK, cool! Do let us know if that works. We’re trying to isolate more of the different types of bugs people encounter setting up environments, as it can be hard to replicate them…
@ainsley Yes it works now. Sorry for the delay, I had to backup then resize my partitions ( Docker uses / so if you have /home on another partition, it’s / you must make space on).