Cannot deploy: context deadline exceeded

Hi there,

I am trying to deploy a very small image (< 50MB) and I cannot do it:

[kurt@paradox terraria]$ fly deploy
==> Verifying app config
--> Verified app config
==> Building image
Remote builder fly-builder-dry-thunder-6876 ready
==> Creating build context
--> Creating build context done
==> Building image with Docker
--> docker host: 20.10.12 linux x86_64
ERRO[0110] Can't add file /home/kurt/go-workspace/audio-academia/fly/terraria/governor to tar: io: read/write on closed pipe 
ERRO[0110] Can't close tar writer: io: read/write on closed pipe 
Error failed to fetch an image or build from source: error building: Error response from daemon: context deadline exceeded


[kurt@paradox terraria]$ fly deploy
==> Verifying app config
--> Verified app config
==> Building image
Remote builder fly-builder-dry-thunder-6876 ready
==> Creating build context
--> Creating build context done
Error failed to fetch an image or build from source: error fetching docker server info: Get "http://[fdaa:0:9f5b:a7b:2656:921f:ecd8:2]:2375/v1.41/info": context deadline exceeded


[kurt@paradox terraria]$ fly deploy
==> Verifying app config
--> Verified app config
==> Building image
Remote builder fly-builder-dry-thunder-6876 ready
==> Creating build context
--> Creating build context done
==> Building image with Docker
--> docker host: 20.10.12 linux x86_64
[+] Building 301.7s (0/1)                                                                          
 => [internal] load remote build context                                                    301.7s

In the last try I aborted after waiting for 5 minutes.

That’s just one example, but I’ve been having problems during the last hours (for instance ssh console very slow or unable to connect, machine api-proxy problems, etc). I did some tests with fly.io a couple of months ago and everything worked so much better; I hope is just a very bad day today or something wrong with my account… Is there any workaround, like building the images myself?

Best,
Kurt.-

We were having an incident a few hours ago, so you might have seen some sub-par performance :sweat_smile: then for sure.

You’re right, there is a workaround to this sort of thing: you can build locally with fly deploy --local-only

Thanks Eli.

Definitely I have to check local image building. I am not very “docker-savvy” and I don’t have a docker server installed (I am using podman right now) but it does not seem very hard.

Today everything worked better and smoother… not perfectly though, there where some little hiccups from time to time (specially when “Sending build context to Docker daemon”… it’s very slow), but it is working quite better.

Best,
Kurt.-