panic: runtime error: invalid memory address or nil pointer dereference about vultr-cli HOT 10 CLOSED

We will dig into the failure a bit more. However its good to know that the binaries on the release page are working fine! We will adjust the vultr-cli version accordingly as since the versions are not matching up.

from vultr-cli.

I will rebuild all of the available Go binaries on the release page for safe measure. Along with taking a look at your docker file and trying to pinpoint why the binary was failing within the container

from vultr-cli.

@tianon We had fixed the binaries and updated the ones on the release page. Thanks for spotting that error!

from vultr-cli.

Hey there @tianon !

You can use your existing API key with no problems.

I just pulled down the the mac binary (vultr-cli_darwin_amd64.tar.gz). This binary was working fine...I also renamed it to vultr-cli (I noticed you were calling executing the binary as vultr-cli) and this was also working fine.

Not sure what the issue might be - I am going to double check to make sure that the linux binaries are running fine. I would recommend to see if you can build from source and have that binary run for you while I look into the linux binaries.

Also what version of Go are you running on your machine?

from vultr-cli.

@tianon

Just tried running the vultr-cli_linux_amd64.tar.gz on Ubuntu 18.04 and it was able to run just fine.

Could you share what Linux distro and version you are currently running on?

from vultr-cli.

I'm on Debian 10 (Buster), although I'm running this inside a Docker container to which I pass my VULTR_API_KEY environment variable (https://github.com/tianon/dockerfiles/blob/564ae5120f13f8b011e5a106267d23d79695b02f/vultr-cli/Dockerfile).

I'll update that to build from source instead and see if that helps. 👍

from vultr-cli.

Building from master via Go 1.12 appears to have worked fine (and I can run commands fine), although I will note the output from my master build's vultr-cli version is Vultr-cli v0.1.0 where the release build I downloaded appears to be Vultr-cli v0.0.1. 😕

from vultr-cli.

Ok, this is fun -- I've adjusted my new build to build from the v0.1.0 tag instead of building straight from master (given that there are basically no real code changes in vultr:d529ad1...vultr:a504997), and it works if I build and run it inside golang:1.12, but if I then copy the binary to another (otherwise mostly empty) image and run it, it fails, which gave me the clue I needed to track this down. If I add the ca-certificates package, it works fine, so it appears that a segfault is the failure mode when it can't verify the certificate of the Vultr API server? 😅

from vultr-cli.

OK, confirmed that the binary downloaded from https://github.com/vultr/vultr-cli/releases/tag/v0.1.0 works as well if I install ca-certificates first, although the failure mode is a little odd and the fact that it reports Vultr-cli v0.0.1. 😅 ❤️ 👍

from vultr-cli.

@tianon

The segfault is caused because theca-certificates were not installed in the dockefile. Since we are making API calls over HTTPs the ca-certificates are required and Go does not bundle this into the binary.

So the way you ran RUN apk add --no-cache ca-certificates in your dockerfile you could have also run RUN apk add --no-cache curl which would also install ca-certificate in the process.

Hopefully this helps clear up the reason for the segfault.

from vultr-cli.