Hide Forgot
Description of problem: I can deploy successfully this Node + HTTP Server Project (https://github.com/obsidian-toaster/generator-frontend/blob/master/README.md#openshift) hosting the Obsidian Front UI within a local OpenShift instance (= VM machine running on my MacOS) but not when I try to launch a build using a OSO Dev machine (https://console.dev-preview-int.openshift.com) npm http fetch GET https://registry.npmjs.org/symbol/-/symbol-0.2.3.tgz npm http fetch 200 https://registry.npmjs.org/symbol/-/symbol-0.2.3.tgz /tmp/scripts/assemble: line 26: 21 Killed npm install --dev --no-progress warning: Failed to remove container "1fc37de74b5f01271e116920a2340c142a029e0a27032e0d050aa50dd12fa629": Error response from daemon: Unable to remove filesystem for 1fc37de74b5f01271e116920a2340c142a029e0a27032e0d050aa50dd12fa629: remove /var/lib/docker/containers/1fc37de74b5f01271e116920a2340c142a029e0a27032e0d050aa50dd12fa629/shm: device or resource busy error: build error: non-zero (13) exit code from ryanj/centos7-s2i-nodejs:current Version-Release number of selected component (if applicable): OpenShift Online - 3.4 How reproducible: Steps to Reproduce: 1. Git clone this project : git:obsidian-toaster/generator-frontend.git 2. Install the template : oc create -f templates/template_s2i.yml 3. Create : oc process front-generator FORGE_URL=http://<FORGE-BACKEND-ROUTE-ADDRESS>/forge | oc create -f - 4. Start a build : oc start-build front-generator-s2i Actual results: error: build error: non-zero (13) exit code from ryanj/centos7-s2i-nodejs:current Expected results: Additional info:
The issue appears to be memory/resource related. Online Ops nor I have been able to reproduce the exact problem but we cannot build the project with the following failures: <--- Last few GCs ---> 2352307 ms: Mark-sweep 1359.6 (1458.1) -> 1358.7 (1458.1) MB, 3177.3 / 0 ms [allocation failure] [GC in old space requested]. 2354579 ms: Mark-sweep 1358.7 (1458.1) -> 1358.6 (1458.1) MB, 2271.9 / 0 ms [allocation failure] [GC in old space requested]. 2357021 ms: Mark-sweep 1358.6 (1458.1) -> 1356.4 (1458.1) MB, 2442.1 / 0 ms [last resort gc]. 2359668 ms: Mark-sweep 1356.4 (1458.1) -> 1357.2 (1458.1) MB, 2646.9 / 0 ms [last resort gc]. <--- JS stacktrace ---> ==== JS stack trace ========================================= Security context: 0x2c1f9ca5a91 <JS Object> 2: /* anonymous */(aka /* anonymous */) [/opt/rh/rh-nodejs4/root/usr/lib/node_modules/spdx-expression-parse/index.js:~3] [pc=0x2ac02d7c857f] (this=0x2c1f9c041b9 <undefined>,argument=0x1ddc0bfff509 <String[3]: MIT>) 3: /* anonymous */ [/opt/rh/rh-nodejs4/root/usr/lib/node_modules/validate-npm-package-license/index.js:36] [pc=0x2ac02d4da807] (this=0x198e33324fc9 <JS Global Object>,argument... FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory /tmp/scripts/assemble: line 26: 23 Aborted (core dumped) npm install --dev --no-progress error: build error: non-zero (13) exit code from centos/nodejs-4-centos7 The stack trace is produced when the build is done under an account with sufficiently larger resources than a regular user in the INT environment.