Error deploying with --remote-only flag

Questions / Help Build debugging
1

I’m receiving this error since yesterday while trying to deploy with --remote-only flag:

Error: failed to fetch an image or build from source: {"message":"You are not authorized to use this builder"}
 (http: 401)

If I destroy the builder image it creates a new one and I’m able to deploy again, but it works only once, so I need to keep destroying it.

CLI version: v0.0.548

fly doctor returns:

Testing authentication token... PASSED
Testing flyctl agent... PASSED
Testing local Docker instance... Nope
Pinging WireGuard gateway (give us a sec)... PASSED
2

When this happens, do you see anything in the builder’s logs?

fly logs -a fly-builder-<unique-name>

3

@pavel This is what I see…

2023-05-01T20:38:15.666 app[6e82e2db026987] mia [info] time="2023-05-01T20:38:15.665618103Z" level=warning msg="Error fetching app remote-army: decoding response: json: cannot unmarshal number into Go struct field GraphQLError.Errors.Path of type string"

2023-05-01T20:38:15.666 app[6e82e2db026987] mia [info] time="2023-05-01T20:38:15.665638230Z" level=debug msg="authorized from api"

2023-05-01T20:38:15.666 app[6e82e2db026987] mia [info] time="2023-05-01T20:38:15.665674027Z" level=info msg="fdaa:1:a334:a7b:159d:0:a:0 - - [01/May/2023:20:38:14 +0000] \"GET /flyio/v1/extendDeadline HTTP/1.1\" 401 57"
4 
 2023-05-01T23:54:17.775 app[4d89791b4e5987] mia [info] Sending signal SIGUSR1 to main child process w/ PID 555

2023-05-01T23:54:17.776 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:17.775818264Z" level=info msg="received SIGUSR1"

2023-05-01T23:54:17.776 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:17.775883887Z" level=debug msg="liveness loop caused deadline reset"

2023-05-01T23:54:18.064 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:18.064131655Z" level=debug msg="checking docker activity"

2023-05-01T23:54:18.064 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:18.064426488Z" level=debug msg="Calling GET /v1.41/containers/json?filters=%7B%22status%22%3A%7B%22running%22%3Atrue%7D%7D&limit=0"

2023-05-01T23:54:18.752 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:18.752420902Z" level=debug msg="Calling HEAD /_ping"

2023-05-01T23:54:18.952 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:18.952488568Z" level=debug msg="Calling HEAD /_ping"

2023-05-01T23:54:19.066 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:19.066182119Z" level=debug msg="checking docker activity"

2023-05-01T23:54:19.066 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:19.066552704Z" level=debug msg="Calling GET /v1.41/containers/json?filters=%7B%22status%22%3A%7B%22running%22%3Atrue%7D%7D&limit=0"

2023-05-01T23:54:19.157 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:19.157502920Z" level=debug msg="Calling HEAD /_ping"

2023-05-01T23:54:19.360 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:19.360413177Z" level=debug msg="Calling HEAD /_ping"

2023-05-01T23:54:19.560 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:19.560384563Z" level=debug msg="Calling HEAD /_ping"

2023-05-01T23:54:19.761 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:19.760730131Z" level=debug msg="Calling HEAD /_ping"

2023-05-01T23:54:20.065 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:20.065399671Z" level=debug msg="authorized from cache"

2023-05-01T23:54:20.065 app[4d89791b4e5987] mia [info] time="2023-05-01T23:54:20.065455987Z" level=info msg="fdaa:1:a334:a7b:159d:0:a:0 - - [01/May/2023:23:54:20 +0000] \"GET /flyio/v1/extendDeadline HTTP/1.1\" 401 57"
5

Thanks! I’ll take a look and update once we have a fix for this.

1 Like
6

@pggalaviz This should be fixed now. You will need to destroy the builder again (hopefully, one last time) and let flyctl create a new one.

1 Like
7

Hey @pavel, it’s working fine now, thank you!!

1 Like
8

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