You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't have a way to share this, but we are trying to use this action on our self-hosted runners, and ran into an issue with opa requiring GLIBC:
Run opa test configuration_rules/ -v
opa test configuration_rules/ -v
shell: /bin/bash -e {0}
opa: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.29' not found (required by opa)
opa: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by opa)
Error: Process completed with exit code 1.
I ended up switching this action out by curl'ing the static binary and adding it to the path, but it would be nice if this action did that as well. Here's my substitution for the setup-opa task:
Thanks for the report! I think it would solve your problem if we added a new input calledstatic to select which binary you need, right?
Something like:
...
static:
description: Install the statically linked version of the OPA binary. Usefull when GLIBC is not installed on self-hosted runners.
required: false
default: false
Hello!
I don't have a way to share this, but we are trying to use this action on our self-hosted runners, and ran into an issue with
opa
requiring GLIBC:I ended up switching this action out by
curl
'ing the static binary and adding it to the path, but it would be nice if this action did that as well. Here's my substitution for thesetup-opa
task:The text was updated successfully, but these errors were encountered: