coolify [Bug]: Heroku buildpack not working

[Bug]: Heroku buildpack not working

Open wallaceosmar opened this issue 1 year ago • 11 comments

Is there an existing issue for this?

[X] I have searched the existing issues

Description

Fail after 2s.

[03:38:30.421] GitHub importer started.
[03:38:30.424] Cloning heroku/python-getting-started:main branch.
[03:38:30.723] Configuration changed.
[03:38:30.750] Building image started.

Steps To Reproduce

create new app
add any heroku example in the git (https://github.com/heroku/python-getting-started)
enable debug log
deploy

Version

3.10.16

Oct 20 '22 06:10 wallaceosmar

To deploy the container I had to force coolify to v3.10.1, I didn't test the exact version it stopped working

Oct 21 '22 03:10 wallaceosmar

I can reproduce it and will fix it in the next version.

Oct 23 '22 09:10 andrasbacsai

@andrasbacsai still not working

Nov 08 '22 12:11 wallaceosmar

I tested it out, and it works for me, or at least the build & deployment are working. But the application states an error, but that is just a python env configuration:

Nov 08 '22 13:11 andrasbacsai

Tested in a new vm in DigitalOcean.

In my server one of the attempts of running show this log

[14:04:49.044] /usr/local/bin/pack: 1: Syntax error: redirection unexpected
[14:04:50.064] 2

Nov 08 '22 14:11 wallaceosmar

Strange, I cannot reproduce it. Can you show me a screenshot of the configuration for this application?

Nov 15 '22 20:11 andrasbacsai

@andrasbacsai after some digging in the source code i discover the pack script is not present in the image and the url to download the pack return a 404

RUN curl -SL https://cdn.coollabs.io/bin/linux/amd64/pack-v0.27.0 -o /usr/local/bin/pack https://github.com/coollabsio/coolify/actions/runs/3479738443/jobs/5818653611#step:8:869

Work around

ssh in the vm to get the container id use sudo docker ps | grep coollabsio/coolify: ssh in the coolify container with sudo docker exec -it {container_id} bash run (curl -sSL "https://github.com/buildpacks/pack/releases/download/v0.27.0/pack-v0.27.0-linux.tgz" | tar -C /usr/local/bin/ --no-same-owner -xzv pack)

Nov 17 '22 23:11 wallaceosmar

Yea clean your docker cache, and you would be able to recreate the problem.

(not sure you should be doing cached runs on release tests)