Error when deploying - Error error connecting to docker: unhandled upstream service error: could not fulfill resource requirements: not enough available dedicated CPUs to fulfill request of 4 cpus

I am following the instructions to deploy a pi-hole from:

Stuff Your Pi-Hole From Anywhere · Fly

I am able to launch the app and generate the fly.toml. However, when I try to deploy I get this error message:

Error error connecting to docker: unhandled upstream service error: could not fulfill resource requirements: not enough available dedicated CPUs to fulfill request of 4 cpus

The Dockerfile is exactly the same as on the blog:

FROM pihole/pihole:latest

ENV INTERFACE eth0
ENV DNSMASQ_LISTENING ALL

And the fly.toml is as follows:

fly.toml file generated for ***-pihole-1 on 2021-11-25T15:28:15-05:00

app = “moo-pihole-1”

kill_signal = “SIGINT”
kill_timeout = 5
processes =

[env]

[experimental]
allowed_public_ports =
auto_rollback = true

[[services]]
http_checks =
internal_port = 8080
processes = [“app”]
protocol = “tcp”
script_checks =

[services.concurrency]
hard_limit = 25
soft_limit = 20
type = “connections”

[[services.ports]]
handlers = [“http”]
port = 80

[[services.ports]]
handlers = [“tls”, “http”]
port = 443

[[services.tcp_checks]]
grace_period = “1s”
interval = “15s”
restart_limit = 0
timeout = “2s”

[[services]]
internal_port = 53
protocol = “udp”

[[services.ports]]
port = “53”

I’ve searched the forum and did a quick google search but I haven’t been able to find anyone running into the same issue. Any help would be much appreciated.

Thanks,
Chris

It looks like the builder app that your account is using isn’t able to find a place to run — you should be able to get a new builder by finding your builder app name by running fly apps list, and you should see one that starts with fly-builder — you can then delete it with fly apps destroy. The next time you try to run a build Fly will make you a new builder elsewhere.

If you have Docker set up locally you could also run fly deploy --local-only to use your local Docker — that way you won’t need a builder on Fly at all.

Thanks for helping with this. I figured it was something to do with the builders, so I made sure to destroy all the apps including the one that started with fly-builder. Once I cleared out the apps, I tried again and it will still erroring out with the same error. I just tried deleting the fly-builder app again and it still isn’t happy. The local-only build is a good workaround for me until I can find a solution. If you happen to have any other thoughts as to what could be going on it will be much appreciated.