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

Can't open openssl.cnf for reading, No such file or directory #693

Closed
tommymonk opened this issue Dec 13, 2022 · 2 comments
Closed

Can't open openssl.cnf for reading, No such file or directory #693

tommymonk opened this issue Dec 13, 2022 · 2 comments

Comments

@tommymonk
Copy link

I'm getting this error with the following config against shogo82148/actions-setup-redis@v1 on a linux self-hosted runner.

      - name: setup redis server dependencies
        run: |
          apt-get -y install zstd
        
      - name: setup redis server
        uses: shogo82148/actions-setup-redis@v1
        with:
          redis-version: '6.x'

MicrosoftTeams-image

@tommymonk
Copy link
Author

tommymonk commented Dec 15, 2022

I've just confirmed that it's working properly on a GitHub runner.

I think someone else discovered that the value of RUNNER_TOOL_CACHE is different between runners;

actions/setup-python#459 (comment)

Self Hosted

Run echo ${RUNNER_TOOL_CACHE}
  echo ${RUNNER_TOOL_CACHE}
  shell: /usr/bin/bash -e {0}
/home/actions/actions-runner/_work/_tool

Hosted

Run echo ${RUNNER_TOOL_CACHE}
  echo ${RUNNER_TOOL_CACHE}
  shell: /usr/bin/bash -e {0}
/opt/hostedtoolcache

This is what I see in both runners;

SELF-HOSTED
RUNNER_TEMP: /opt/actions-runner/_work/_temp
RUNNER_TOOL_CACHE: /opt/actions-runner/_work/_tool

HOSTED
RUNNER_TEMP: /home/runner/work/_temp
RUNNER_TOOL_CACHE: /opt/hostedtoolcache

@shogo82148 I think you need to review the directory used for temp ?

@shogo82148
Copy link
Owner

I've check the binaries only on the GitHub-hosted runners.
We need to build them as portable binaries to run self-hosted runners, however I don't know how to do that.

shogo82148 added a commit that referenced this issue Dec 30, 2022
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