Now I’m getting a error while building the changes.
2022-10-25T18:04:24.234 app[24740d36] yul [info] Preparing to run: `/cnb/process/rcapibridge` as 1000
2022-10-25T18:04:24.249 app[24740d36] yul [info] 2022/10/25 18:04:24 listening on [fdaa:0:a775:a7b:b729:2474:d36:2]:22 (DNS: [fdaa::3]:53)
2022-10-25T18:29:55.878 runner[1f030eed] yyz [info] Starting instance
2022-10-25T18:29:56.530 runner[1f030eed] yyz [info] Configuring virtual machine
2022-10-25T18:29:56.554 runner[1f030eed] yyz [info] Pulling container image ```
What could cause this ?
Here is my fly status :
Why the instances are not able to "run" it keep them selfs running in "pending" mode.
App
Name = johndoe
Owner = district-web
Version = 13
Status = running
Hostname = johndoe.fly.dev
Platform = nomad
Deployment Status
ID = UUID
Version = v13
Status = running
Description = Deployment is running pending automatic promotion
Instances = 3 desired, 1 placed, 0 healthy, 0 unhealthy
Instances
ID PROCESS VERSION REGION DESIRED STATUS HEALTH CHECKS RESTARTS CREATED
e0ee88cf app 13 ⇡ yyz run pending 0 2m21s ago
We found an issue that was impacting our registry in yyz – a stale DNS entry for an upstream service was causing connections to hang. We fixed the issue and things are looking better on our side. If you’re still seeing issues let us know!