issues with fly deploy
@kapa.ai im having fly deploy issues where it hangs up on depot builder. There seems to be work arounds using flyctl deploy --depot=false but that doesnt sem to work with wasp. any thoughts?
4 Replies
Hi @wbjb. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
I'm sorry, but the knowledge sources do not contain specific information about issues with the Fly.io depot builder or using the --depot=false flag with Wasp's deployment commands. There is no mention of configuring or bypassing the depot builder in the Wasp CLI documentation or community discussions provided.
The documentation does mention that Wasp defaults to using a remote Fly.io builder for deployments, and you can opt to build locally by supplying the --build-locally option to wasp deploy fly launch or wasp deploy fly deploy. However, there is no reference to the --depot flag or workarounds for depot-related issues in the context of Wasp deployments. If you are experiencing persistent issues, you might consider trying the --build-locally option as an alternative:
But please note, this is the only relevant workaround mentioned in the sources, and there is no guarantee it will address depot-specific problems. For further troubleshooting, you may want to consult the official Fly.io or Wasp community channels for up-to-date advice or report the issue if it persistsDeploying with the Wasp CLI.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @wbjb, 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?
@kapa.ai i think that worked to use the --build local
Let me check the knowledge base for you again. One moment! :books:
----------------------
Great to hear that using the --build-locally option worked for you! According to the Wasp documentation, supplying --build-locally to wasp deploy fly launch or wasp deploy fly deploy allows you to build your Docker container locally instead of using the default remote builder, which can help avoid issues related to the remote build process on Fly.io Deploying with the Wasp CLI.
If you encounter any further issues or have more questions about deploying with Wasp, feel free to ask!
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @wbjb, 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?
Hey @wbjb, can you share some logs and error messages? Did you maybe try to deploy something else to fly, out of Wasp?
Fly often has issues which are resolved after a while, please double check if that's the case 🙂