I am experiencing this issue for the first time on multiple builds triggered from a Github Action with no other changes.
==> Verifying app config
--> Verified app config
==> Building image
Waiting for remote builder fly-builder-quiet-cherry-3988...
Error failed to fetch an image or build from source: error connecting to docker: failed building options: Validation failed: Pubkey has already been taken, Name has already been taken
I’ve deleted and re-created a builder and the error remains.
Can confirm I just tried another build moments ago and it is the same error.
Waiting for remote builder fly-builder-quiet-cherry-3988...
Error failed to fetch an image or build from source: error connecting to docker: failed building options: Validation failed: Pubkey has already been taken, Name has already been taken
This error means the wireguard pubkey and name aren’t getting sent properly. But I don’t understand what would cause that, unless the Github environment changed somehow! We’re going to have to dig through code.
We’re having the same issue on builds triggered from a Github Action. When I re-run the job it works. I think this happens since a day or two. We also haven’t touched the fly.toml or deploy.yaml file.
We’ve been working on this, along with some API slowness.
Are you all still seeing these problems? I can’t get a GitHub action to fail. It’s possible this was related to slow API requests but I’m not sure how that would have correlated.
That error seems to have gone but app is still pending multiple versions that never finish deploying and the github action doesn’t complete.
App
Name = mg1
Owner = personal
Version = 68
Status = running
Hostname = mg1.fly.dev
Deployment Status
ID = 09e4e7ef-4cf4-0726-6e06-a9d616f15ef4
Version = v68
Status = running
Description = Deployment is running pending automatic promotion
Instances = 1 desired, 1 placed, 0 healthy, 0 unhealthy
Instances
ID PROCESS VERSION REGION DESIRED STATUS HEALTH CHECKS RESTARTS CREATED
c4a191da app 68 ⇡ dfw run pending 0 1m0s ago
cc4387c9 app 67 dfw stop pending 0 5m39s ago
19ffbcfb app 66 dfw stop pending 0 2h38m ago
26106eb7 app 64 mia(B) run running 0 5h23m ago
Oh good catch, that was unrelated. Our orchestration was trying to schedule VMs to hardware we deprovisioned. Should be fixed now, if you’re still seeing “pending” it’ll clear up over time.
@kurt I am seeing this error crop up again in the last 2 hours on one of my applications ‘enterprise-ui’. Just wanted to alert you in case anything needs to be reviewed.