Yep +1 on needing the larger memory builders on Depot
2 Likes
Depot builders are back now for everyone. We’re closely monitoring build performance along with the Depot team.
One exception: apps using buildpacks will still use our older builders. Check your fly.toml to see if you’re using them. If you want to move off them to Dockerfile-based builds, post here for help!
Those of you on paid support plans should already be using larger builders, just as you had been using before. Once we start work on builder pricing, we’ll update you on how to get larger builders.
2 Likes
I’ve been deploying my Node.js app without a Dockerfile with no issues. But now when I run fly deploy using the heroku/builder:24 builder I’m getting:
Error: failed to fetch an image or build from source: app does not have a Dockerfile or buildpacks configured. See App configuration (fly.toml) · Fly Docs
Running fly deploy --depot=false is working for me. Does this mean I have to use a Dockerfile now?
Which version of flyctl are you using? The latest should automatically fall back to la Fly builder for Buildpacks.
To use Depot builders you do need a Dockerfile.
1 Like
Since the switch I’m having issues where it gets stuck on “Waiting for depot builder…” and never progresses.
Sometimes this happens in the middle of a build for seemingly no reason.
I don’t know how I would verify whether or not this is Depot’s fault but my builds which never took more than ~4-5 minutes now also frequently stop progressing and go on for up to 30 minutes. Never happened before.
EDIT: This turned out to be an error in my build, it’s just that with Depot the error message never surfaces and it appears to keep running forever.
My builds are getting stuck. I have tried both with default depot and --depot=false. Builds never complete. I have to try 4-5 times when one random build succeeds. Never happened before.
I ran fly version upgrade, which upgraded me from v0.3.2 → v0.3.6. However, it’s still requiring me to have a Dockerfile
Can you post your build section from fly.toml?
[build]
builder = "heroku/builder:24"
Hey, yeah from machine logs, it looks like one of the builds ended up deadlocking the build host for a bit while trying to process a RUN pnpm run build step, which blocked logs and other builds from progressing.
Do you know what the fix ended up being on your end? If you have any additional details, we may be able to add some automated protection against this happening again.
Hello @joshua-fly – do you have ETA on when the bigger builders/we can customize our builders on depot? We’re still getting some out of memory issues with depot but that should resolved if we can assign larger builders/have multiple
I did a couple fly deploys four days ago on 9/19 and they worked. Last night on 9/23 I got the error Error: failed to fetch an image or build from source: app does not have a Dockerfile or buildpacks configured. See https://fly.io/docs/reference/configuration/#the-build-section.
The solution for me was to use the solution fly deploy --depot=false as given in this answer. I didn’t have to touch the previously-working toml file which was fine. Needless to say I’m relieved at this solution.
I’m only repeating this because this appears to be a brand new issue and none of the other suggestions I found on the internet worked and I’m hoping this helps make it higher up in the search results.
1 Like
OK, thanks. If you specify a buildpack, then you should get the Fly builder. Only specifying a builder was an oversight that we’ll fix in the next flyctl release.
1 Like
You can run multiple builders already using the --depot-scope=app option. If you need more CPU/memory (beyond your current 8cpu/8GB), drop a message to Fly.io support.
1 Like
I am literally having the same issue right now. Would be nice to know how to fix this.
1 Like
Trying Depot builders with --depot-scope app with three apps in parallel in my GitHub Action and I still get the same inconsistent failures as I did with Fly builders but this time with a new error
==> Building image
Waiting for depot builder...
Error: failed to fetch an image or build from source: error building: timed out connecting to machine: failed to list workers: Unavailable: connection error: desc = "transport: authentication handshake failed: EOF"
sigh
…back to BuildJet for now
Woke up this morning and now my CI suddenly is broken, blocking us. This is in arn with --ha=false and --remote-only if that matters.
Validating fly.pull-request.toml
✓ Configuration is valid
--> Verified app config
==> Building image
Waiting for depot builder...
==> Building image with Depot
--> build: ()
#1 [internal] load build definition from Dockerfile
#1 DONE 0.0s
#1 [internal] load build definition from Dockerfile
#1 transferring dockerfile: 587B 0.2s done
#1 DONE 0.2s
#2 [internal] load metadata for docker.io/library/alpine:latest
#2 DONE 1.0s
#3 [internal] load .dockerignore
#3 transferring context: 2B 0.1s done
#3 DONE 0.1s
#4 [1/7] FROM docker.io/library/alpine:latest@sha256:beefdbd8a1da6d2915566fde36db9db0b524eb737fc57cd1367effd16dc0d06d
#4 resolve docker.io/library/alpine:latest@sha256:beefdbd8a1da6d2915566fde36db9db0b524eb737fc57cd1367effd16dc0d06d done
#4 sha256:43c4264eed91be63b206e17d93e75256a6097070ce643c5e8f0379998b44f170 3.62MB / 3.62MB 0.1s done
#4 extracting sha256:43c4264eed91be63b206e17d93e75256a6097070ce643c5e8f0379998b44f170 0.1s done
#4 DONE 0.2s
#5 [3/7] ADD https://github.com/pocketbase/pocketbase/releases/download/v0.20.1/pocketbase_0.20.1_linux_amd64.zip /tmp/pb.zip
#5 CANCELED
#6 [2/7] RUN apk add --no-cache unzip openssh
#6 CANCELED
#7 [internal] load build context
#7 transferring context: 81.33kB 0.3s done
#7 CANCELED
==> Building image
Waiting for depot builder...
Error: failed to fetch an image or build from source: error building: timed out connecting to machine: failed to list workers: Unavailable: connection error: desc = "transport: authentication handshake failed: EOF"
Error: Process completed with exit code 1.
EDIT: I appended --depot false and now it works. Please do not remove this opt out possibility until all issues have been resolved and things have settled down.
That’s annoying! We’ll take a look. There are no plans to remove the opt-out anytime soon.
1 Like
@Saeed and @simpledjanogdev, Flyctl 0.3.7 contains a fix for fly.toml that only specify a builder. Can you give it a spin?
1 Like