Really struggling with deploy
Hi all - I've been building a Wasp app for the last two months while teaching myself coding. I'm almost done my app on local. I am really struggling with the deploy. I'm working off an M2 Silicon Chip Macbook Pro, and I've tried a ton of things. TL;DR, I'm trying Heroku, but even when trying the specific instructions for M2, it still didn't work.
Tried downgrading Docker to a less current version, but I am unsure which version to downgrade to, and it seems that Docker also has version limitations with M2.
I get the following error when I use the command: heroku container:push --app XXXXX web
failed commit on ref "manifest-sha256:4ef768618e84c07096a616d01666cfa6f86a14305c94ea1172a120fafa52edf8": unexpected status from PUT request to https://registry.heroku.com/v2/XXXXX/web/manifests/latest: 405 Method Not Allowed
I then tried this set of commands:
docker buildx build --platform linux/amd64 -t XXXXX .
docker tag <app-name> registry.heroku.com/XXXXX/web
docker push registry.heroku.com/XXXXX/web
I then got this error:
failed commit on ref "manifest-sha256:c70a80797778e384a7eebbee9653cf38d9b823a26b92c47e43b518b9032d97cd": unexpected status from PUT request to https://registry.heroku.com/v2/XXXXX/web/manifests/latest: 405 Method Not Allowed
Both attempts had this warning:
1 warning found (use docker --debug to expand):
- LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 50)
I tried circumventing these issues by using Colima, but that did not work either.
I'm using Wasp version 0.15.0, and Docker Desktop 4.36.0, Docker Compose v2.30.3-desktop.1.
P.S. I did try Fly.io already; It was working for a bit but they had some outages a few weeks ago which broke my config. I then did some further research and learned that fly.io is not super reliable sometimes.
Any suggestions on how to handle this?
Tried downgrading Docker to a less current version, but I am unsure which version to downgrade to, and it seems that Docker also has version limitations with M2.
I get the following error when I use the command: heroku container:push --app XXXXX web
failed commit on ref "manifest-sha256:4ef768618e84c07096a616d01666cfa6f86a14305c94ea1172a120fafa52edf8": unexpected status from PUT request to https://registry.heroku.com/v2/XXXXX/web/manifests/latest: 405 Method Not Allowed
I then tried this set of commands:
docker buildx build --platform linux/amd64 -t XXXXX .
docker tag <app-name> registry.heroku.com/XXXXX/web
docker push registry.heroku.com/XXXXX/web
I then got this error:
failed commit on ref "manifest-sha256:c70a80797778e384a7eebbee9653cf38d9b823a26b92c47e43b518b9032d97cd": unexpected status from PUT request to https://registry.heroku.com/v2/XXXXX/web/manifests/latest: 405 Method Not Allowed
Both attempts had this warning:
1 warning found (use docker --debug to expand):
- LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 50)
I tried circumventing these issues by using Colima, but that did not work either.
I'm using Wasp version 0.15.0, and Docker Desktop 4.36.0, Docker Compose v2.30.3-desktop.1.
P.S. I did try Fly.io already; It was working for a bit but they had some outages a few weeks ago which broke my config. I then did some further research and learned that fly.io is not super reliable sometimes.
Any suggestions on how to handle this?
