How to deploy new version without interrupting background jobs?

[halfer]

@khuezy

I don’t know if you can do a broad deploy and not have it kill the existing instances.

True, a deploy would not work here. But a local image build and a push would likely work; I assume this would help:

Push to Fly.io image registry via Docker API

I’d like to use Docker’s API to build my image and then push the image to my Fly.io app’s registry. Is this possible? I see that the docker api has a header we can use for authentication, but Fly.io seems to require using the command line to push an image to the Fly.io registry. I’d like to avoid using the Fly CLI for this process if possible.

(I don’t mean the API bit, but the registry auth stuff. Maybe there is an image push in the flyctl CLI too, I don’t know.)