Deploy from Github fails but succeeds from console

1

I have a deploy to a staging environment that succeeds when I do a fly deploy. However, it always fails from my github action on my deploy step.

unknown: {“errors”:[{“code”:“NAME_UNKNOWN”, “message”:“app repository not found”}]}

That is all I have to go on. It is hard to tell from the output where it fails. I see output from my Dockerfile that it gets to my ENTRYPOINT command. It may go past that I just don’t know. More output from my the fly deploy log is:

#19 writing image sha256:54a546dd6ba20ea38ce6d93e90651f076e5b7db486a76e186bda27bf77bcf553 done

801#19 naming to registry.fly.io/sellect-inference-engine-staging:44488af done

#19 writing image sha256:54a546dd6ba20ea38ce6d93e90651f076e5b7db486a76e186bda27bf77bcf553 done

801#19 naming to registry.fly.io/sellect-inference-engine-staging:44488af done

802#19 DONE 16.5s

803The push refers to repository [registry.fly.io/sellect-inference-engine-staging]

8040b957dfa93eb: Preparing

8054ec6c571f83d: Preparing

…
…
…
unknown: {“errors”:[{“code”:“NAME_UNKNOWN”, “message”:“app repository not found”}]}

1092Error: Process completed with exit code 1.

This happens after 4 retries of each of the shas (container ids ???)

Any help is appreciated. Searches of this error messages have not been helpful. I can’t see what is working from the console and what is not from the github action. My production deploys are identical other than the hostnames and container registries and they are working.

2

How did you generate your token? fly token create <wat>. Did you properly set this in your GH Actions Secrets?

3

Yes. I did. I can try and regenerate this and change it. I used deploy in place of <wat> as my creation argument. Perhaps I should have done org as an org deploy token?

4

Yes. I did. I can try and regenerate this and change it. I used deploy in place of <wat> as my creation argument. Perhaps I should have done org as an org deploy token?

5

deploy should have been the right flag, but try using an org token.

6

Oh man. Sorry for the dupe.

7

Okay. I used an org token and that seemed to solve the problem. Is there some implicit rule that github action keys should be org tokens for fly? For my production token I don’t recall if it was an org token.

8

Cool, I think deploy is per app, eg the -a flag for the specific app (or where ever you run that command, it will auto detect the app name via the fly.toml). In your case, org makes sense for deploying all apps under your org.

9

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