A blast from the past... can't deploy a new release

Hi there y’all?
Anybody also not being able to deploy to production today?

fly doctor

… says everything is fine…
… status page says all green…

fly deploy

Sorry you can’t…

The current error is this:

[+] Building 49.8s (12/25)                                                                                                                                      
 => [internal] load build definition from Dockerfile                                                                                                       1.0s
 => => transferring dockerfile: 32B                                                                                                                        1.0s
 => [internal] load .dockerignore                                                                                                                          1.0s
 => => transferring context: 35B                                                                                                                           1.0s
 => resolve image config for docker.io/docker/dockerfile:experimental                                                                                      2.2s
 => CACHED docker-image://docker.io/docker/dockerfile:experimental@sha256:600e5c62eedff338b3f7a0850beb7c05866e0ef27b2d2e8c02aa468e78496ff5                 0.0s
 => [internal] load metadata for quay.io/evl.ms/fullstaq-ruby:3.1.4-jemalloc-slim                                                                          1.1s
 => [base 1/6] FROM quay.io/evl.ms/fullstaq-ruby:3.1.4-jemalloc-slim@sha256:082a112f02357732fa3cf3b2c756ff7a51604230e2ff76de9dc6b86ec72dd5f3               0.0s
 => ERROR [internal] load build context                                                                                                                   40.6s
 => => transferring context: 1.31MB                                                                                                                       40.6s
 => CACHED [base 2/6] RUN mkdir /app                                                                                                                       0.0s
 => CACHED [base 3/6] WORKDIR /app                                                                                                                         0.0s
 => CACHED [base 4/6] RUN mkdir -p tmp/pids                                                                                                                0.0s
 => CACHED [base 5/6] RUN curl https://get.volta.sh | bash                                                                                                 0.0s
 => CANCELED [base 6/6] RUN volta install node@16.13.1 && volta install yarn                                                                              40.7s
 > [internal] load build context:
Error: failed to fetch an image or build from source: error building: failed to solve: rpc error: code = Canceled desc = grpc: the client connection is closing

Oh: I’ve deleted remote builder and still failing…
So… docker!!! fly!!! remote-docker!!!

Anyway… I guess I have to spend a few hours figuring out what is happening.
Stay tunned!

If anybody is having the issue, please say Hi!

The deploy Gods were on my side this sunny afternoon!
fly deploy is back working, and

But on my Linux desktop, fly lost its link with my local docker…
That saved me a few months ago!

So, tomorrow I will spend sometime getting --local-only to work again on my Linux!

And to be precise and fair: I do believe the issue was my local wifi connection.
After I’ve switched my internal wifi network, fly deployed worked!

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.