{"action":"created","issue":{"url":"https://api.github.com/repos/jupyter-incubator/dashboards_nodejs_app/issues/47","repository_url":"https://api.github.com/repos/jupyter-incubator/dashboards_nodejs_app","labels_url":"https://api.github.com/repos/jupyter-incubator/dashboards_nodejs_app/issues/47/labels{/name}","comments_url":"https://api.github.com/repos/jupyter-incubator/dashboards_nodejs_app/issues/47/comments","events_url":"https://api.github.com/repos/jupyter-incubator/dashboards_nodejs_app/issues/47/events","html_url":"https://github.com/jupyter-incubator/dashboards_nodejs_app/issues/47","id":130730504,"number":47,"title":"Struggling to get make 'make run' and 'make run-tmpnb' to run on linux 14.04","user":{"login":"Analect","id":4063815,"avatar_url":"https://avatars.githubusercontent.com/u/4063815?v=3","gravatar_id":"","url":"https://api.github.com/users/Analect","html_url":"https://github.com/Analect","followers_url":"https://api.github.com/users/Analect/followers","following_url":"https://api.github.com/users/Analect/following{/other_user}","gists_url":"https://api.github.com/users/Analect/gists{/gist_id}","starred_url":"https://api.github.com/users/Analect/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Analect/subscriptions","organizations_url":"https://api.github.com/users/Analect/orgs","repos_url":"https://api.github.com/users/Analect/repos","events_url":"https://api.github.com/users/Analect/events{/privacy}","received_events_url":"https://api.github.com/users/Analect/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2016-02-02T16:12:04Z","updated_at":"2016-02-04T08:40:21Z","closed_at":"2016-02-03T08:46:30Z","body":"Thanks for your efforts on this repo ... I'm watching it with interest ... however:\r\n\r\nI ran `make run` ... which appeared to succeed in building images and then launching containers ... I'm not sure if the `bower install` step didn't get run properly or something ... the terminal logs would suggest maybe it's missing express (see logs lower down)\r\n\r\nThe screen that is meant to list notebooks was blank ... and this is what shows up for the simple notebook.\r\n![image](https://cloud.githubusercontent.com/assets/4063815/12754448/3654e6b0-c9c3-11e5-8d1d-25f6eb850621.png)\r\n\r\n```\r\n-- Starting proxy container\r\nnpm info it worked if it ends with ok\r\nnpm info using npm@3.3.12\r\nnpm info using node@v5.5.0\r\nnpm info lifecycle node-deployed-dashboard@0.0.1~prestart: node-deployed-dashboard@0.0.1\r\nnpm info lifecycle node-deployed-dashboard@0.0.1~start: node-deployed-dashboard@0.0.1\r\n\r\n> node-deployed-dashboard@0.0.1 start /home/node/app\r\n> node ./bin/www\r\n\r\nGET / 302 49.128 ms - 64\r\nGET /notebooks 200 240.792 ms - 281\r\nSTACK: Error: Not Found\r\n    at /home/node/app/app.js:106:15\r\n    at Layer.handle [as handle_request] (/home/node/app/node_modules/express/lib/router/layer.js:95:5)\r\n    at trim_prefix (/home/node/app/node_modules/express/lib/router/index.js:312:13)\r\n    at /home/node/app/node_modules/express/lib/router/index.js:280:7\r\n    at Function.process_params (/home/node/app/node_modules/express/lib/router/index.js:330:12)\r\n    at next (/home/node/app/node_modules/express/lib/router/index.js:271:10)\r\n    at /home/node/app/node_modules/express/lib/router/index.js:618:15\r\n    at next (/home/node/app/node_modules/express/lib/router/index.js:256:14)\r\n    at Function.handle (/home/node/app/node_modules/express/lib/router/index.js:176:3)\r\n    at router (/home/node/app/node_modules/express/lib/router/index.js:46:12)\r\nGET /sw-import.js?baseURI=http%3A%2F%2Flocalhost%3A3000%2Fbower_components%2Fplatinum-sw%2Fplatinum-sw-register.html&clientsClaim=true&defaultCacheStrategy=networkFirst&importscript=http%3A%2F%2Flocalhost%3A3000%2Fbower_components%2Fplatinum-sw%2Fbootstrap%2Fsw-toolbox-setup.js&precache=&skipWaiting=true&version=1.0 404 13.974 ms - 878\r\nSTACK: Error: Not Found\r\n```\r\nI tried to stop and restart the **dashboard-proxy** container, so that I might troubleshoot things manually inside the container ... but `ctrl-c` of the `make run` process appears to kill and remove that container.\r\n\r\nI don't have that much experience with `make`, but each time a run that command, it appears to build a whole new image ... which obviously isn't as slow as the first time, as it uses caches etc ... but is there scope for getting this working using `docker-compose`, especially once the images are built?\r\n\r\nWhen running `make run-tmpnb` I also hit a hurdle on it complaining that port 8000 is already being used ... Although I have other docker containers running ... none of them is touching port 8000 ... does this 1005/node on port 8000 look like anything related to this set-up?\r\n\r\n```\r\nStep 21 : CMD start\r\n ---> Using cache\r\n ---> 0e8b480a3420\r\nSuccessfully built 0e8b480a3420\r\n4eb7912c7e6fd15e096e18a8036bd476fd1c27c2dc831c084037d6286a6d3662\r\nError response from daemon: Cannot start container 4eb7912c7e6fd15e096e18a8036bd476fd1c27c2dc831c084037d6286a6d3662: failed to create endpoint tmpnb-proxy on network bridge: Error starting userland proxy: listen tcp 0.0.0.0:8000: bind: address already in use\r\nmake: *** [run-tmpnb-proxy] Error 1\r\nmccoole@mccoole-ubuntu-W520:~/Development/Tools/jupyter/dashboards_nodejs_app$ netstat -tulpn | grep 8000\r\n(Not all processes could be identified, non-owned process info\r\n will not be shown, you would have to be root to see it all.)\r\ntcp        0      0 0.0.0.0:8000            0.0.0.0:*               LISTEN      1005/node\r\n```"},"comment":{"url":"https://api.github.com/repos/jupyter-incubator/dashboards_nodejs_app/issues/comments/179710001","html_url":"https://github.com/jupyter-incubator/dashboards_nodejs_app/issues/47#issuecomment-179710001","issue_url":"https://api.github.com/repos/jupyter-incubator/dashboards_nodejs_app/issues/47","id":179710001,"user":{"login":"Analect","id":4063815,"avatar_url":"https://avatars.githubusercontent.com/u/4063815?v=3","gravatar_id":"","url":"https://api.github.com/users/Analect","html_url":"https://github.com/Analect","followers_url":"https://api.github.com/users/Analect/followers","following_url":"https://api.github.com/users/Analect/following{/other_user}","gists_url":"https://api.github.com/users/Analect/gists{/gist_id}","starred_url":"https://api.github.com/users/Analect/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Analect/subscriptions","organizations_url":"https://api.github.com/users/Analect/orgs","repos_url":"https://api.github.com/users/Analect/repos","events_url":"https://api.github.com/users/Analect/events{/privacy}","received_events_url":"https://api.github.com/users/Analect/received_events","type":"User","site_admin":false},"created_at":"2016-02-04T08:40:21Z","updated_at":"2016-02-04T08:40:21Z","body":"@parente \r\nThanks for the extra colour above.\r\nI try to piece together (often from the monthly jupyter.hackpad.com monthly sessions) the various initiatives that are happening under the jupyter project, which seem too numerous to count!\r\nI'm really interested in what your IBM group are doing vis a vis some of this incubator stuff, but it's not clear to me if/when this will get folded back into Jupyter core (or if indeed that's even the plan), since there are now a whole bunch of ipywidgets and services that are intended as plugins ...\r\n\r\nThere's obviously also the work happening on phosphorjs, but as an outsider looking in, it's still hard to see how that is tying back in ... maybe all will be revealed in version 5.0 of the notebook, which seems like it's pushing to leverage javascript as the front-end on top of the various kernels that Jupyter exposes.\r\n\r\nIn the meantime, I install repos like this to try to learn a little more!  It would be great to have a diagram of how everything in the eco-system is planned to hang together ... a view from 30,000ft, if you like! I know that's probably not your responsibility ... but as one of the more active collaborators on the project, you have a perspective better than most ... and you write well, as per your blogs."}}