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
When executing the k6exec container with the following command:
docker run --rm -i k6exec:latest -v run - < examples/combined.js
I encounter the following error:
time="2025-01-18T08:30:12Z" level=error msg="build error: Get \"https://registry.k6.io/catalog.json\": tls: failed to verify certificate: x509: certificate signed by unknown authority" app=k6exec
Steps to Reproduce
Pull the latest version of the k6exec Docker image.
Save an example script as examples/combined.js.
Run the following command:
docker run --rm -i k6exec:latest -v run - < examples/combined.js
The command fails with a TLS certificate verification error:
tls: failed to verify certificate: x509: certificate signed by unknown authority
Additional Information
It seems the issue is related to the TLS certificate verification when accessing https://registry.k6.io/catalog.json. This might be caused by:
A missing or untrusted Certificate Authority (CA).
An outdated or improperly configured certificate in the k6exec container.
Please provide guidance on resolving this issue or clarify if additional configuration is required.
The text was updated successfully, but these errors were encountered:
Description
When executing the
k6exec
container with the following command:docker run --rm -i k6exec:latest -v run - < examples/combined.js
I encounter the following error:
Steps to Reproduce
docker run --rm -i k6exec:latest -v run - < examples/combined.js
Expected Behavior
The command should execute successfully, connecting to https://registry.k6.io/catalog.json without TLS-related errors.
Actual Behavior
The command fails with a TLS certificate verification error:
Additional Information
It seems the issue is related to the TLS certificate verification when accessing
https://registry.k6.io/catalog.json
. This might be caused by:Please provide guidance on resolving this issue or clarify if additional configuration is required.
The text was updated successfully, but these errors were encountered: