deploy rendertron on heroku #90
Comments
|
Before you pushed the container to heroku, did it run without errors locally? Based on the error message, I'm wondering if did indeed build (it shouldn't be throwing the CHROME_PATH error). I don't generally use heroku, but everything about the container should be fine based on heroku's requirements. I'll spin up a test account and see if I can get it to work. |
|
I was able to run the docker container successfully by using
the image should be fine |
|
@hekod777 Cool, appreciate the verification. Let me see if I can scope out what Heroku is doing when it pushes to their container repository. |
|
@justinribeiro Had the same error when I tried to run After install chrome as ec2-user, the error was gone But I got another error after
These two lines will appear first
then the error will came up in about 8 secs after some digging, the root of the problem is thats the in chrome-launcher any ideas what might be the problem? The purpose of npm start instead of running docker containerrunning docker container will result in a very poor performance. I am trying to use npm start to start rendertron and see if it can perform better. Reproduction steps
Tried work arounds
|
|
i'm getting a similar stack trace when trying to push to heroku, no mention of the CHROME_PATH in the logs for me tho and it deploys fine locally 2017-09-26T20:05:48.573836+00:00 heroku[web.1]: State changed from crashed to starting 2017-09-26T20:06:06.282687+00:00 heroku[web.1]: Starting process with command `run start` 2017-09-26T20:06:09.241688+00:00 heroku[web.1]: Process exited with status 1 2017-09-26T20:06:09.253670+00:00 heroku[web.1]: State changed from starting to crashed 2017-09-26T20:06:09.255325+00:00 heroku[web.1]: State changed from crashed to starting 2017-09-26T20:06:09.160736+00:00 app[web.1]: 2017-09-26T20:06:09.160751+00:00 app[web.1]: Usage: npm 2017-09-26T20:06:09.160752+00:00 app[web.1]: 2017-09-26T20:06:09.160753+00:00 app[web.1]: where is one of: 2017-09-26T20:06:09.160754+00:00 app[web.1]: ddp, dedupe, deprecate, dist-tag, docs, doctor, edit, 2017-09-26T20:06:09.160753+00:00 app[web.1]: access, adduser, bin, bugs, c, cache, completion, config, 2017-09-26T20:06:09.160755+00:00 app[web.1]: explore, get, help, help-search, i, init, install, 2017-09-26T20:06:09.160755+00:00 app[web.1]: install-test, it, link, list, ln, login, logout, ls, 2017-09-26T20:06:09.160756+00:00 app[web.1]: outdated, owner, pack, ping, prefix, prune, publish, rb, 2017-09-26T20:06:09.160756+00:00 app[web.1]: rebuild, repo, restart, root, run, run-script, s, se, 2017-09-26T20:06:09.160757+00:00 app[web.1]: search, set, shrinkwrap, star, stars, start, stop, t, team, 2017-09-26T20:06:09.160757+00:00 app[web.1]: test, tst, un, uninstall, unpublish, unstar, up, update, v, 2017-09-26T20:06:09.160758+00:00 app[web.1]: version, view, whoami 2017-09-26T20:06:09.160760+00:00 app[web.1]: npm help search for help on 2017-09-26T20:06:09.160758+00:00 app[web.1]: 2017-09-26T20:06:09.160761+00:00 app[web.1]: npm help npm involved overview 2017-09-26T20:06:09.160759+00:00 app[web.1]: npm -h quick help on 2017-09-26T20:06:09.160759+00:00 app[web.1]: npm -l display full usage info 2017-09-26T20:06:09.160761+00:00 app[web.1]: 2017-09-26T20:06:09.160763+00:00 app[web.1]: or on the command line via: npm --key value 2017-09-26T20:06:09.160762+00:00 app[web.1]: Specify configs in the ini-formatted file: 2017-09-26T20:06:09.160764+00:00 app[web.1]: 2017-09-26T20:06:09.160762+00:00 app[web.1]: /app/.npmrc 2017-09-26T20:06:09.160763+00:00 app[web.1]: Config info can be viewed via: npm help config 2017-09-26T20:06:09.160765+00:00 app[web.1]: npm@5.3.0 /nodejs/lib/node_modules/npm 2017-09-26T20:06:26.707851+00:00 heroku[web.1]: Starting process with command `run start` 2017-09-26T20:06:29.650430+00:00 heroku[web.1]: State changed from starting to crashed 2017-09-26T20:06:29.644361+00:00 heroku[web.1]: Process exited with status 1 2017-09-26T20:06:29.569145+00:00 app[web.1]: 2017-09-26T20:06:29.569164+00:00 app[web.1]: Usage: npm 2017-09-26T20:06:29.569165+00:00 app[web.1]: 2017-09-26T20:06:29.569165+00:00 app[web.1]: where is one of: 2017-09-26T20:06:29.569166+00:00 app[web.1]: access, adduser, bin, bugs, c, cache, completion, config, 2017-09-26T20:06:29.569167+00:00 app[web.1]: ddp, dedupe, deprecate, dist-tag, docs, doctor, edit, 2017-09-26T20:06:29.569168+00:00 app[web.1]: explore, get, help, help-search, i, init, install, 2017-09-26T20:06:29.569168+00:00 app[web.1]: install-test, it, link, list, ln, login, logout, ls, 2017-09-26T20:06:29.569169+00:00 app[web.1]: outdated, owner, pack, ping, prefix, prune, publish, rb, 2017-09-26T20:06:29.569170+00:00 app[web.1]: rebuild, repo, restart, root, run, run-script, s, se, 2017-09-26T20:06:29.569170+00:00 app[web.1]: search, set, shrinkwrap, star, stars, start, stop, t, team, 2017-09-26T20:06:29.569171+00:00 app[web.1]: test, tst, un, uninstall, unpublish, unstar, up, update, v, 2017-09-26T20:06:29.569171+00:00 app[web.1]: version, view, whoami 2017-09-26T20:06:29.569172+00:00 app[web.1]: 2017-09-26T20:06:29.569173+00:00 app[web.1]: npm -h quick help on 2017-09-26T20:06:29.569174+00:00 app[web.1]: npm -l display full usage info 2017-09-26T20:06:29.569174+00:00 app[web.1]: npm help search for help on 2017-09-26T20:06:29.569175+00:00 app[web.1]: npm help npm involved overview 2017-09-26T20:06:29.569175+00:00 app[web.1]: 2017-09-26T20:06:29.569176+00:00 app[web.1]: Specify configs in the ini-formatted file: 2017-09-26T20:06:29.569177+00:00 app[web.1]: /app/.npmrc 2017-09-26T20:06:29.569177+00:00 app[web.1]: or on the command line via: npm --key value 2017-09-26T20:06:29.569178+00:00 app[web.1]: Config info can be viewed via: npm help config 2017-09-26T20:06:29.569178+00:00 app[web.1]: 2017-09-26T20:06:29.569179+00:00 app[web.1]: npm@5.3.0 /nodejs/lib/node_modules/npm this is all a bit new to me but i'll ask around to see if anyone has ideas and follow up if they do |
|
@hekod777 It will probably help even if using Docker, but I think you need to add that buildpack and re-deploy |
|
I solved this using heroku-buildpack-google-chrome and #111 (comment) |
|
**I could not publish the project on Heroku. Here my build log:** -----> Node.js app detected -----> Installing binaries -----> Restoring cache -----> Build failed ! Push rejected, failed to compile Node.js app. |
|
For what it's worth, I got up and running on Heroku using the previously mentioned buildpack. But I needed to do a few extra things so I want to document them here: This assumes you've started a Heroku app and are interacting with it via the Heroku CLI. First, add the Google Chrome buildpack to your project: Next, add the $ heroku buildpacks:add heroku/nodejs -a <app-name>Then, update the {
...
"engines": {
"node": "10.15.1",
"npm": "6.4.1"
},
...
}This was helpful in getting past a Next, enter a new script into your {
"scripts": {
...,
"heroku-postbuild": "npm run build"
}
}This will make sure to build rendertron into Finally, add a web: node bin/rendertronThis worked for me and now I have a rendertron app running a node web server for free on Heroku. |
|
I guess the lack of activity and the success stories around the buildpack mean that this is sorted? |
I was trying to deploy my own rendertron docker container to heroku.
the docker image was successfully built
heroku container:push webwas successful as wellbut when I visit the site. It gives an error. this is what i saw in the heroku logs
I am a total newbie in terms of docker.
I'd like to know what went wrong.
thx!
The text was updated successfully, but these errors were encountered: