new abra install json error #406

New Issue

codegod100 · 2023-02-11T14:55:15Z

codegod100 commented

2023-02-11 14:55:15 +00:00

vera@zenbook:~$ abra server ls --debug
FATA[0000] unexpected end of JSON input                  caller="/drone/src/cli/server/list.go:27 glob..func2" stack="/drone/src/cli/server/list.go:27                         glob..func2\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:524     HandleAction\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:173 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:405     (*App).RunAsSubcommand\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:378 Command.startApp\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:102 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:277     (*App).Run\n/drone/src/cli/cli.go:199                                RunApp\n/drone/src/cmd/abra/main.go:22                           main\n/usr/local/go/src/runtime/proc.go:250                    main\n/usr/local/go/src/runtime/asm_amd64.s:1594               goexit"

``` vera@zenbook:~$ abra server ls --debug FATA[0000] unexpected end of JSON input caller="/drone/src/cli/server/list.go:27 glob..func2" stack="/drone/src/cli/server/list.go:27 glob..func2\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:524 HandleAction\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:173 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:405 (*App).RunAsSubcommand\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:378 Command.startApp\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:102 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:277 (*App).Run\n/drone/src/cli/cli.go:199 RunApp\n/drone/src/cmd/abra/main.go:22 main\n/usr/local/go/src/runtime/proc.go:250 main\n/usr/local/go/src/runtime/asm_amd64.s:1594 goexit" ```

codegod100 added the

bug

label 2023-02-11 14:55:15 +00:00

codegod100 commented

2023-02-11 15:15:04 +00:00

This might be due to using windows WSL as my localhost. Running WSL Ubuntu fyi. I ran from the Docker client and didn't get this error. Not sure if red herring or if useful information

decentral1se commented

2023-02-11 21:42:10 +00:00

Hey @codegod100, not seen that one before! Unsure myself what could be the cause of this. Does docker context ls work for you? I have no experience with WSL, so not sure I can help much if that is part of the cause.

Hey @codegod100, not seen that one before! Unsure myself what could be the cause of this. Does `docker context ls` work for you? I have no experience with WSL, so not sure I can help much if that is part of the cause.

codegod100 commented

2023-02-12 02:53:59 +00:00

vera@zenbook:~$ docker context ls
unexpected end of JSON input

I think we found the problem 👍

``` vera@zenbook:~$ docker context ls unexpected end of JSON input ``` I think we found the problem 👍

codegod100 commented

2023-02-12 03:13:03 +00:00

Looks like an open issue on docker's end https://github.com/docker/for-win/issues/13180

codegod100 closed this issue

2023-02-12 04:28:27 +00:00

decentral1se referenced this issue from a commit

2023-02-12 12:28:57 +00:00

docs: WSL note

decentral1se commented

2023-02-12 12:29:58 +00:00

Thanks for following up @codegod100, I've patched docs over in 9a62aaabae to hopefully help others if they run into this.

Thanks for following up @codegod100, I've patched docs over in https://git.coopcloud.tech/coop-cloud/docs.coopcloud.tech/commit/9a62aaabaecc5316ff6856c771126d18681d7651 to hopefully help others if they run into this.

❤️ 1

daniel commented

2023-11-21 16:56:27 +00:00

I am using

WSL version: 2.0.9.0 and
Docker Desktop 4.25.1

and do not seem to have this issue, meaning that I can successfully execute abra server ls --debug

The folks over at https://github.com/docker/for-win/issues/13180 also claim to have merged the fix in Docker 4.17.

I am using - WSL version: 2.0.9.0 and - Docker Desktop 4.25.1 and do not seem to have this issue, meaning that I can successfully execute `abra server ls --debug` The folks over at https://github.com/docker/for-win/issues/13180 also claim to have merged the fix in Docker 4.17.

Sign in to join this conversation.

No Milestone

No project

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#406