-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Hi @fev1n could you share your complete Dockerfile so I can try to understand and reproduce your issue? I've the impression that you're installing Hurl as a npm dependencies. As this installation is inside a Linux container, on an ARM platform (Apple M1/2), the Hurl node package try to install the Linux ARM variant (which we don't provide BTW). One thing you can test is to install Hurl as a native binary in your Docker. For instance, if your Docker base image is a Debian, you can install like this https://hurl.dev/docs/installation.html#debian-ubuntu. Depending on your base image, Hurl installation can vary. Then, in your This way, there'll be less layer and it will be easier to debug. With your Dockerfile, I can try to test it. You can check also our tutorial on CI/CD integration, that may help you => https://hurl.dev/docs/tutorial/ci-cd-integration.html |
Beta Was this translation helpful? Give feedback.
Hi @fev1n could you share your complete Dockerfile so I can try to understand and reproduce your issue?
I've the impression that you're installing Hurl as a npm dependencies. As this installation is inside a Linux container, on an ARM platform (Apple M1/2), the Hurl node package try to install the Linux ARM variant (which we don't provide BTW). One thing you can test is to install Hurl as a native binary in your Docker. For instance, if your Docker base image is a Debian, you can install like this https://hurl.dev/docs/installation.html#debian-ubuntu. Depending on your base image, Hurl installation can vary. Then, in your
package.json
, you can call it with"test": "hurl *.hurl"
instead of"…