flyctl deploy not working

Questions / Help
1

I am trying do deploy (before it worked), and now i get this error always
ERROR [internal] load build context
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
I need some help, i can send my settings, but not sure that reason in my setting, because it worked one month ago, maybe i need update something?

5 Likes
2

Hi,
i have the same issue,
and cannot fix it
can someone help?

2 Likes
3

Hey there,

When you say it worked before (1 month ago) do you mean that same app was previously deployed at one point? If that same app was deployed previously and now it won’t deploy (and you haven’t touched any of the code/made changes) then I would look at what flyctl version you are running and possibly updating- flyctl version upgrade · Fly Docs

Also would you mind posting your fly.toml file (without envs included) so we can get a better look into what’s going on?

4

I am Currently facing the same issue.

I am currently on the latest version as flyctl version gives flyctl.exe v0.1.68 windows/amd64 Commit: 8a1757c2e652cc3c2a4d90280ab6ac021e7b1919 BuildDate: 2023-07-31T23:06:21Z .

My fly.toml is

app = "frenbox-launch"
primary_region = "atl"
console_command = "/code/manage.py shell"

[deploy]
  release_command = "python manage.py migrate"

[env]
  PORT = "8000"

[http_service]
  internal_port = 8000
  force_https = true
  auto_stop_machines = true
  auto_start_machines = true
  min_machines_running = 0

[[statics]]
  guest_path = "/code/static"
  url_prefix = "/static/"

It used to work untill i upgraded.

1 Like
5

Experiencing the same issue on a Django project without changes to toml or docker files. Mac with Intel chip

[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

fly deploy or fly deploy --local-only rendered the same error.
Only flyctl --remote-only ended up working.

2 Likes
6

Same issue here. The same error.

I tried it a few times, but neither fly deploy --local-only or --remote-only are working.

I did update to the last flyctl version, but it did not solve the problem.

@kaelynH

7

Hello, @peterakande. Have you managed to solve the issue?

8

It sounds like there might a problem with the recent change to BuildKit, but I can’t reproduce it, so I’m not certain.

Do you know what version last worked for you? Maybe try downgrading to the release just before the BuildKit change (0.1.158) and see if that unblocks you, like this. Note that flyctl will attempt to upgrade itself if it’s out of date, so you’ll need to disable that until you’re back on latest w/ fly settings autoupdate disable

3 Likes
9

For future readers:

downgrade fly to v0.1.58

curl -L https://fly.io/install.sh | sh -s -- v0.1.58

That did the trick. The autoupdate didn’t allow the deploy using older versions like 0.1.58.

The deploy is working OK now.

4 Likes
10

I actually had to resort to using github actions to deplot my app on pushing to a specific git repo.

1 Like
11

fly deploy by default works like fly deploy --remote-only. So it is odd to see that both fly deploy and fly deploy --local-only were failing. Could you share the output of fly deploy --local-only?

Seems slightly different since even --remote-only doesn’t work for you. Could you sahre the output of fly deploy --remote-only?

12

FWIW I just had this problem multiple times while on the road using 4G.

As soon as I got to 5G, it was fine.

13

I think I have a similar problem but the error message I get is a little different:

failed to fetch an image or build from source: error building: failed to dial gRPC: rpc error: code = Internal desc = rpc error: code = Internal desc = header key “x-docker-expose-session-name” contains value with non-printable ASCII characters

but none of the above mentioned solutions worked for me

can anybody help me?

1 Like
14

Thank you! Had the same issue, can confirm that downgrading to 0.1.58 fixed deployments.

1 Like
15

downgrading does not work for me, as the the auto updater immediately kicks in and it’s not possible to disable it on the old version… it’s a real pain not being able to deploy. @michael any official guidance on this bug?

1 Like
16

Sorry for the inconvenience.

Did you get 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 (like @Firin981) or failed to fetch an image or build from source: error building: failed to dial gRPC: rpc error: code = Internal desc = rpc error: code = Internal desc = header key “x-docker-expose-session-name” contains value with non-printable ASCII characters (like @danilo-nilsantos)?

17

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

18

hiding because it recommends downgrading flyctl, which is no longer relevant