David Randall

The current exporter uses this command. Can you please provide the output the device in question? Obscure sensitive data. ```bash smartctl --json --info --health --attributes --tolerance=verypermissive --nocheck=standby --format=brief --log=error ```...

Hi @pokab. Addressing PR #205 is first priority. Then I will look at this PR. Thank you for your patience.

Hi @pshirshov. Is this still an issue? I ran your JSON thru the current exporter and it did not produce any errors.

Yup. arm64 was built in the latest release.

Thanks for catching that @jfcoz. The title and OP doesn't mention Docker. Let's fix that.

@SuperQ Can you elaborate on this issue? I couldn't find a related issue in the Prometheus common repo. From PR #78 ([link][]): > The problem is alpine doesn't tag their...

Adding the response here to keep the thread. @jfcoz PR #150 didn't work. The [prometheuscommunity/smartctl-exporter](https://hub.docker.com/r/prometheuscommunity/smartctl-exporter/tags) image shows 2 hashes for `linux/amd64`.  Meanwhile, [prometheuscommunity/smartctl-exporter-linux-arm64](https://hub.docker.com/r/prometheuscommunity/smartctl-exporter-linux-arm64/tags) has a `linux/amd64` os/arch.  I'm...

@stepanbaghdasaryan This issue is to provide a multi-architecture build in [prometheuscommunity/smartctl-exporter][1]. PR #150 did not fix the mutli-arch build and thus was reverted. However, in hind sight, I see it...

@SuperQ Can you give me access to the `prometheuscommunity` organization on CircleCI so I can troubleshoot the build process? Any insight into the build process is also appreciated.

@SuperQ Do you mind if I make this a feature branch so others can work on it and iron out the details? I don't have any devices for testing.