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'm attempting to transition our openresty images from Alpine to Debian currently. However, we have a single module, NAXSI, that we load into our image which we were historically adding as part of the compile step as a dynamic module.
The new debian images are no longer doing the compile in the Dockerfile but are instead expecting the user to use opm to install additional modules. However, the module I'm attempting to install does not have an opm package of their module: wargio/naxsi#114
In other versions of the Dockerfile it seems that this could be done through something like REST_CONFIG_OPTIONS_MORE
I'm attempting to transition our openresty images from Alpine to Debian currently. However, we have a single module, NAXSI, that we load into our image which we were historically adding as part of the compile step as a dynamic module.
The new debian images are no longer doing the compile in the Dockerfile but are instead expecting the user to use
opm
to install additional modules. However, the module I'm attempting to install does not have anopm
package of their module: wargio/naxsi#114In other versions of the Dockerfile it seems that this could be done through something like
REST_CONFIG_OPTIONS_MORE
docker-openresty/jammy/Dockerfile
Line 54 in 30682c9
which is no longer available in the Debian images as far as I can tell.
What would be the best way to go about building a Docker image that has a third party package installed without utilizing
opm
?The text was updated successfully, but these errors were encountered: