-
Notifications
You must be signed in to change notification settings - Fork 3
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
Unable to Load Module on M1 Mac #15
Comments
I suspect this is not specific to an M1 chip since it is all just Linux behavior. It may be related to the path you are copying the module to, which is different depending on the Linux distro. Hopefully the deployment resources will help you to structure your Docker deployment and resolve your issue:
According to this deployment testing we did at Curity, these are the locations for each of the distros:
Try downloading the file at this URL and then saving it to the Then run this command to deploy NGINX and the module: ./resources/deployment/deploy.sh amazon2 Then run this command to test all module operations: ./resources/deployment/test.sh |
Thanks Gary, I'll get one of the team with a Mac to give this a go 👍🏻 |
Using a docker image of nginx 1.21.3 on a Mac with an M1 chip we are unable to load the module. Error message:
nginx: [emerg] dlopen() "/etc/nginx/modules/ngx_curity_http_oauth_proxy_module.so" failed (/etc/nginx/modules/ngx_curity_http_oauth_proxy_module.so: cannot open shared object file: No such file or directory) in /etc/nginx/nginx.conf:7
The module itself is mounted to the correct location, so I assume it is a dependency that cannot be found.
Tried with amzn, amzn2 and Ubuntu modules. We've also previously tried an Alpine image with the Alpine module, but we've had issues with other Alpine images on M1 before so kind of expected that to fail.
Does the module need to be compiled specifically for machines with the M1 chip?
The text was updated successfully, but these errors were encountered: