-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Bug]: Nixpacks build.sh not copied to /artifacts
directory
#3442
Comments
@UltraSive it builds fine, try deploy from a new project |
It's not about the actual repo I linked its rather than wherever I build using nixpacks it can't run the build.sh file like I described. |
I'm not following. The repo you linked did not have this issue it built fine using nixpacks there was no issue with the build.sh file |
It's not about the repo I linked, It's a problem with one of my projects having an issue with not generating the output for nixpacks correctly such that everything in that project wont build regardless of the git repo it's linked to. I'm pretty familiar with nixpacks as I use it every day building tekton pipelines so if I can find the issue I will and make a pull request, I just haven't been able to find the issue quite yet so I opened an issue here to make note of it. |
I'm having this experience too on beta332 and then beta335, with your minimal reproduction link and my own Astro deployment from a private Github deployment type. Attempted from a new resource/project multiple times. Edit: also ran into the same build.sh error on trying to build from dockerfile. |
I have a few ideas what could cause this. The next version (releasing today) probably fix it, but if not, I also added a build.sh content to the debug build logs in the next version. Potential fix #3425 |
This is happening to me with Next.js on beta347. |
it's still an issue any github project I used (nixpacks)
|
OMG, so for some reason when I deployed my site under project called API's it doesn't deploy. |
@gilbertlucas46 you cant use a single quote in project name |
I updated to beta360 and it works now, built my next.js app with Nixpacks just fine. |
Description
Exec's into the build container
There is no /artifacts/build.sh like there is referenced in in the logs to start the build
It appears there are some hidden steps to the build commands not shown in the deployment debug log, and it seemingly has a issue there.
Minimal Reproduction (if possible, example repository)
https://github.com/UltraSive/sveltekit-test
Exception or Error
Version
v4.0.0-beta.335
Cloud?
The text was updated successfully, but these errors were encountered: