Today I started getting this message while deploying:
Which makes me ask: why is my work migrated to v2, if it’s highly experimental in your own words? Past 6 months already have been unstable with Fly.io, I really don’t get why do you so frequently break deployments.
Once again, I’m unable to deploy my product. Here’s the logs;
6ffbe69d3edb: Layer already exists 8a6340798fb6: Layer already exists ee7b22c10358: Layer already exists 8faaf641728a: Layer already exists 92a4e8a3140f: Layer already exists deployment-01H1F: digest: sha256:d207558 size: 1576 --> Pushing image done image: registry.fly.io/xxxx:deployment-yyyy image size: 151 MB ? This feature is highly experimental and may produce unexpected results. Proceed? Yes Running release command: /app/bin/migrate ✓ Deploying with rolling strategy ✓ Error failed to wait for VM 21781955a10e89 in started state: deadline_exceeded: machine failed to reach desired state, started, currently created
Any ideas how do I solve this?