Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XVFB Binaries failed to compile on Heroku push #1

Open
andersr opened this issue Jan 10, 2015 · 2 comments
Open

XVFB Binaries failed to compile on Heroku push #1

andersr opened this issue Jan 10, 2015 · 2 comments

Comments

@andersr
Copy link

andersr commented Jan 10, 2015

Hi - I am using your build pack with Heroku Buildpack Multi in my Rails app. However, I get the following when attempting to push to heroku:

 git push heroku master
Counting objects: 1341, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (1254/1254), done.
Writing objects: 100% (1341/1341), 2.26 MiB | 89.00 KiB/s, done.
Total 1341 (delta 254), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote: 
remote: -----> Fetching custom git buildpack... done
remote: -----> Multipack app detected
remote: =====> Downloading Buildpack: https://github.com/douglasjsellers/heroku-xvfb-buildpack.git
remote: =====> Detected Framework: xvfb
remote: -----> Fetching XVFB binaries at https://s3.amazonaws.com/heroku.buildpacks/xvfb.tar.bz2
remote: -----> Extracting XVFB binaries to /tmp/build_7ba69ae9a5b4734039196c73f024a5b9/vendor/xvfb
remote: /tmp/buildpackDYQEz/bin/compile: 26: /tmp/buildpackDYQEz/bin/compile: sudo: not found
remote: 
remote:  !     Push rejected, failed to compile Multipack app

This is my .buildpacks file:

https://github.com/douglasjsellers/heroku-xvfb-buildpack.git
https://github.com/stomita/heroku-buildpack-phantomjs.git
https://github.com/heroku/heroku-buildpack-ruby.git

I do not get any errors when pushing to heroku without the XVFB buildpack added.
Any ideas you might have as to why this compile issue is occurring? The "sudo" seems to imply that it might be a permissions issue of some sort.

Thanks in advance for any insights!

@ninjakx
Copy link

ninjakx commented Sep 24, 2017

Found any solution?

@iqbalcrat
Copy link

any solution for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants