Deployment error 01GBK6H67328AHA1955QQ4A8XY-lax

Questions / Help
1

Request ID in subject line.

Hi. Any idea what is happening with this?

(project is smokescreen-ldg)

flyctl deploy -r lax
==> Verifying app config
→ Verified app config
==> Building image
Remote builder fly-builder-dark-lake-4133 ready
==> Creating build context
→ Creating build context done
==> Building image with Docker
→ docker host: 20.10.12 linux x86_64
Sending build context to Docker daemon 6.512kB
[+] Building 0.7s (12/12) FINISHED
=> CACHED [internal] load remote build context 0.0s
=> CACHED copy /context / 0.0s
=> [internal] load metadata for Docker Hub 0.7s
=> [internal] load metadata for Docker Hub 0.7s
=> [builder 1/4] FROM Docker Hub 0.0s
=> [stage-1 1/3] FROM Docker Hub 0.0s
=> CACHED [builder 2/4] WORKDIR /go/src/app 0.0s
=> CACHED [builder 3/4] COPY . . 0.0s
=> CACHED [builder 4/4] RUN go build . 0.0s
=> CACHED [stage-1 2/3] COPY --from=builder /go/src/app/smokescreen /usr/local/bin/smokescreen 0.0s
=> CACHED [stage-1 3/3] COPY acl.yaml /etc/smokescreen/acl.yaml 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:a40ee42afa77b71e8ce6f1c851737bad25da8d03cfdcaaaa11fa26459ea45c3a 0.0s
=> => naming to registry.fly.io/smokescreen-ldg:deployment-01GBK6H257M3VRREJA8WWFHK5G 0.0s
→ Building image done
==> Pushing image to fly
The push refers to repository [registry.fly.io/smokescreen-ldg]
75a389340187: Layer already exists
100538f7d86b: Layer already exists
e722d396f503: Layer already exists
deployment-01GBK6H257M3VRREJA8WWFHK5G: digest: sha256:91ab6c4a91c22ab18b7a58bbb38db22bd3b74cfb579d0af04d1e65598611662b size: 947
→ Pushing image done
image: registry.fly.io/smokescreen-ldg:deployment-01GBK6H257M3VRREJA8WWFHK5G
image size: 74 MB
==> Creating release
Error You ran into an error connecting to the Fly API. If the error persists, keep this request ID to help Fly Support track it down: 01GBK6H67328AHA1955QQ4A8XY-lax

Am authenticated and was able to deploy to my other VM just minutes ago.

Thanks!

2

By the way, just now, I was able to deploy the same app almost verbatim to another VM. The only change was the name of the app in fly.toml. I will leave previous VM up in case it helps fly’s tech support figure out what was going wrong.

3

I’m still curious about why the deployment failed. Meanwhile to keep this VM around in order to facilitate debugging is using up part of my quota…

4

BTW I’m definitely considering paying fly.io for some additional resources. I’m here partly to see what support looks like.

5

This was an error response from our API, probably related to load at the time. We’ve had some API stability issues since last week due to an influx of Heroku users.

1 Like