Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

binaries-location not working as expected #64

Closed
danhngo-lx opened this issue Aug 15, 2023 · 3 comments
Closed

binaries-location not working as expected #64

danhngo-lx opened this issue Aug 15, 2023 · 3 comments

Comments

@danhngo-lx
Copy link

I use this to install promtool:

      - name: Install promtool
        uses: jaxxstorm/action-install-gh-release@v1.10.0
        with:
          repo: prometheus/prometheus
          tag: 'v2.37.9'
          platform: linux
          arch: amd64
          cache: enable
          binaries-location: prometheus-2.37.9.linux-amd64

However when using promtool, the command is not found. I tried to echo $PATH and could see:

/opt/hostedtoolcache/prometheus/prometheus/v2.37.9/linux-amd64:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/runner/.local/bin

I think the path for prometheus should be /opt/hostedtoolcache/prometheus/prometheus/v2.37.9/linux-amd64/prometheus-2.37.9.linux-amd64 instead of /opt/hostedtoolcache/prometheus/prometheus/v2.37.9/linux-amd64? 🤔

I'm using github runner self-hosted by the way.

@jaxxstorm
Copy link
Owner

When you extract the archive, how does the result directory structure look?

@danhngo-lx
Copy link
Author

danhngo-lx commented Aug 28, 2023

The directory looks like this:

prometheus-2.37.9.linux-amd64
├── LICENSE
├── NOTICE
├── console_libraries
│   ├── menu.lib
│   └── prom.lib
├── consoles
│   ├── index.html.example
│   ├── node-cpu.html
│   ├── node-disk.html
│   ├── node-overview.html
│   ├── node.html
│   ├── prometheus-overview.html
│   └── prometheus.html
├── prometheus
├── prometheus.yml
└── promtool

3 directories, 14 files

@jaxxstorm jaxxstorm mentioned this issue Jan 5, 2024
@jaxxstorm
Copy link
Owner

jaxxstorm commented Jan 5, 2024

I was unable to reproduce this on a github hosted runner, so i suspect the issue is related to your self-hosted runner. Considering this closed, as unable to reproduce with a test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants