# Sensu-install missing on docker image

**URL:** https://discourse.sensu.io/t/sensu-install-missing-on-docker-image/1558
**Category:** Sensu Go
**Created:** [January 6, 2020, 5:49pm UTC](https://discourse.sensu.io/t/sensu-install-missing-on-docker-image/1558 "2020-01-06T17:49:30Z")
**Posts on this page:** 1
**Showing post:** 39

<div class="post-metadata">

### Author: ![billm](https://avatars.discourse-cdn.com/v4/letter/b/839c29/32.png) [@billm](https://discourse.sensu.io/u/billm)
#### Post date: [January 9, 2020, 7:43pm UTC](https://discourse.sensu.io/t/sensu-install-missing-on-docker-image/1558/39 "2020-01-09T19:43:01Z")

</div>

@jspaleta I was basically following the hello world example here:

> [@The "Hello World" of Sensu Assets](https://discourse.sensu.io/t/the-hello-world-of-sensu-assets/1422):
>
> In this tutorial, I’ll walk you through packaging up a pretty standard bash script. The goal here is to show that you can take some of those scripts that are hanging around in the nooks and crannies of your organization and package them up as assets. The Setup hello-world.sh #!/bin/sh STRING="Hello World" echo $STRING if [$? -eq 0]; then exit 0 else exit 2 fi The first step is to ensure that our directory structure is in place. As noted in [Sensu Go example asset structure](https://docs.sensu.io/sensu-go/latest/reference/assets/#example-structure), our sc…

But simply taring up the asset and creating a github release for it doesn’t seem to be what gets generated, in for example, @aaronsachs “releases” on his github:

[https://github.com/asachs01/sensu-plugins-plivo/releases](https://github.com/asachs01/sensu-plugins-plivo/releases)

so all the different arch tar balls? I have no idea where those come from.

@jspaleta so you’re still working on this then? Thanks for that.

---

_[View the full topic](https://discourse.sensu.io/t/sensu-install-missing-on-docker-image/1558)._