error deploying using fly.io
29.21 npm ERR! In file included from ../libusb/libusb/os/linux_usbfs.c:26:
29.21 npm ERR! ../libusb/libusb/os/linux_usbfs.h:24:10: fatal error: linux/magic.h: No such file or directory
29.21 npm ERR! 24 | #include <linux/magic.h>
29.21 npm ERR! | ^~~~~~~
29.21 npm ERR! compilation terminated.
29.21 npm ERR! make: *** [libusb.target.mk:158: Release/obj.target/libusb/libusb/libusb/os/linux_usbfs.o] Error 1
29.21 npm ERR! gyp ERR! build error
29.21 npm ERR! gyp ERR! stack Error: make failed with exit code: 2
29.21 npm ERR! gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:203:23)
29.21 npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:517:28)
29.21 npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:292:12)
29.21 npm ERR! gyp ERR! System Linux 6.12.8-fly
29.21 npm ERR! gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
29.21 npm ERR! gyp ERR! cwd /app/node_modules/usb
29.21 npm ERR! gyp ERR! node -v v18.18.0
29.21 npm ERR! gyp ERR! node-gyp -v v9.4.0
29.21 npm ERR! gyp ERR! not ok
29.21
29.21 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2025-01-26T11_14_39_065Z-debug-0.log
flyctl deploy --remote-only
i get this error when trying to deploy to fly.io i ran command flyctl deploy --remote-only
3 Replies
Hi @Professorr-X.. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Wohooo @Professorr-X., you just became a Waspeteer level 1!
----------------------
Based on the error message you've provided, it seems you're encountering an issue while deploying your Wasp application to Fly.io. The error appears to be related to a missing Linux header file during the build process. Unfortunately, the knowledge sources provided don't contain specific information about this particular error.
However, I can offer some general advice based on the available information about deploying Wasp apps to Fly.io:
1. First, make sure you're using the latest version of Wasp. You can check your version by running
wasp version and upgrade if necessary as mentioned in the Discord support thread.
2. If you're using a custom Dockerfile, ensure it's properly configured. As mentioned in the Wasp documentation, you can customize the Dockerfile used for deployment.
3. Double-check that all necessary environment variables are set correctly on Fly.io. You can use the flyctl secrets list command to view the current secrets (environment variables) set for your app.
4. If the issue persists, you might want to try the Wasp CLI deployment method instead of manual deployment. The Wasp documentation on CLI deployment provides instructions on how to deploy with a single command:
This command automates several steps and might help avoid some manual configuration issues.
5. If you continue to face issues, it might be helpful to share more details about your project setup or reach out to the Wasp community on Discord for more specific assistance.
Remember, when deploying, it's important to ensure that your local development environment and the deployment environment are as similar as possible to avoid unexpected issues.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Professorr-X., I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?