René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"BrowserStack Local version 8.1 is broken in container environments","articleBody":"Our CI build started to fail due to `browserstack-local` throwing these errors:\r\n\r\n```\r\nConnecting BrowserStack local..\r\nundefined:1\r\nTue Sep 01 2020 14:26:45 GMT+0000 (UTC) -- Container runtime environment detected\r\n^\r\n\r\nSyntaxError: Unexpected token T in JSON at position 0\r\n    at JSON.parse (\u003canonymous\u003e)\r\n    at /root/\u003cfoo\u003e/node_modules/browserstack-local/lib/Local.js:59:23\r\n    at ChildProcess.exithandler (child_process.js:295:7)\r\n    at ChildProcess.emit (events.js:196:13)\r\n    at maybeClose (internal/child_process.js:1011:16)\r\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:268:5)\r\n```\r\n\r\nAs these randomly started, I suspect the `BrowserStackLocal` binary was updated with a broken version, as it doesn't seem to be pinned to a particular one. Manually starting the binary shows log messages in `stdout`, which probably shouldn't be there since `browserstack-local` expect valid JSON:\r\n\r\n```\r\nbash-4.4# /root/.browserstack/BrowserStackLocal --version 2\u003e/dev/null\r\nTue Sep 01 2020 14:31:19 GMT+0000 (UTC) -- Container runtime environment detected\r\nTue Sep 01 2020 14:31:19 GMT+0000 (UTC) -- Attaching services to public interface\r\nBrowserStack Local version 8.1\r\n```\r\n\r\nI'm running `browserstack-local-nodejs` v1.4.5 as v1.4.6 is broken as pointed out in https://github.com/browserstack/browserstack-local-nodejs/commit/7e73b1f3cda85eab79ced321b41cdef141831ce0#r41945904, but manually patching v1.4.6 still shows the same issue.\r\n\r\nThis happens on Alpine Linux within a Docker container, hence the \"Container runtime environment detected\". The issue seems limited to container environments as running the v8.1 outside a container does not show the logs, and doesn't break `browserstack-local`.\r\n\r\n----\r\n\r\nIn the future it would be great if the version of the BrowserStack binary could be pinned to a particular `browserstack-local` one, instead of the last version of the binary being randomly fetched as it is the case currently, causing CI builds to unexpectedly break.","author":{"url":"https://github.com/laurentgoudet","@type":"Person","name":"laurentgoudet"},"datePublished":"2020-09-01T14:45:06.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":10},"url":"https://github.com/114/browserstack-local-nodejs/issues/114"}