Issues deploying first app (stuck on flyctl launch)

Hi there,

I follow the steps in the docs to deploy my first app.
It is a go app based on this doc.
When I run:

➜ flyctl launch
An existing fly.toml file was found for app drio-fly-test
App is not running, deploy...
==> Building image
Remote builder fly-builder-shy-smoke-5052 ready
==> Building image with Buildpacks
--> docker host: 20.10.12 linux x86_64
base: Pulling from paketobuildpacks/builder
Digest: sha256:fa845bc26af36d4b64b43eee7075c7b982462ee043fe64e2928c2905c9940074
Status: Image is up to date for paketobuildpacks/builder:base
base-cnb: Pulling from paketobuildpacks/run
Digest: sha256:ec0263dc98a8c785f4a6750597de8857efd2852fc6544494ff2598426cf7143c
Status: Image is up to date for paketobuildpacks/run:base-cnb
latest: Pulling from paketo-buildpacks/go
Digest: sha256:3c091e92643fe2674aa9b2572983c0e46b47a2aadbf2e0a3bf0891cab3ad55c6
Status: Image is up to date for

flyctl gets stucked without making any progress. I don’t see any traffic on my nic. Not sure what may be happening.

I am using:

➜ flyctl version
flyctl v0.0.450 darwin/arm64 Commit: 51325e4a BuildDate: 2023-01-13T21:54:03Z


After a few minutes the process continues successfully (see below).
I think the issue was that docker could not pull the and the timeout was set pretty high. I think I had to wait for 5 minutes or so.

Adding layer 'paketo-buildpacks/ca-certificates:helper'
Adding layer 'paketo-buildpacks/go-build:targets'
Adding 1/1 app layer(s)
Adding layer 'launcher'
Adding layer 'config'
Adding layer 'process-types'
Adding label 'io.buildpacks.lifecycle.metadata'
Adding label ''
Adding label 'io.buildpacks.project.metadata'
Setting default process type 'fly-test'
*** Images (1c8a1d6e97a8):
Adding cache layer 'paketo-buildpacks/go-dist:go'
Adding cache layer 'paketo-buildpacks/go-build:gocache'
--> Building image done
==> Pushing image to fly
The push refers to repository []
cc7fca46dd1c: Pushed
a3999b6f3189: Pushed
b0ab7e0bbf67: Pushed
7352fc1e0d52: Pushed
d6fe581e986c: Pushed
d8355a9bda2e: Pushed
6f8ed43c84ce: Pushed
1027d3da0925: Pushed
f1c909e2bf15: Pushed
b7c2e91e6139: Pushed
e3c2cb4a2758: Pushed
e611c118f9a4: Pushed
101b05ef38e1: Pushed
deployment-01GQ5VVM8KVESQFJHEF7X95C6S: digest: sha256:98ccba1c7e4f8e6af40b94b6383b270d62d647f173a4d8d0ff048090384e3233 size: 3030
--> Pushing image done
image size: 102 MB
==> Creating release
--> release v2 created

--> You can detach the terminal anytime without stopping the deployment
==> Monitoring deployment

 1 desired, 1 placed, 1 healthy, 0 unhealthy [health checks: 1 total, 1 passing]
--> v0 deployed successfully
1 Like

That long pause is when buildpacks is resolving all the steps for each builder. This can take some serious time unfortunately. We suggest folks use a Dockerfile to get faster builds and smaller images.

1 Like