How is Docker Kong dependencies managed? luarocks 3.11.1 and their recent issues

[cuotos]

With the issue in Luarocks and their manifest being too large to be handled and causing an error, I'm confused as to how any fixes got worked.... my understanding

kong:3.8.0-ubuntu
kong:3.9.0-ubuntu
And
kong:3.9.1-ubuntu

all run the identical versions of luarocks (3.11.1) and LuaJIT.

It appears the luarocks is provided as part of the Kong deb.

How come, now, if you try and run a "luarocks install ", in 3.80 or 3.9.0 you get the "manifest is too large" error, but with kong 3.9.1 you get an error that luarocks requires curl or wget. but its the same versions throughout...

Interestingly luarocks needs curl or wget even if you are downloading the rock and installing the package "from local".

Can anyone help me understand the relationships of these version, as luarocks 3.11.1 appears to behave differently in the kong 3.9.1 image...

Luarocks 3.12 was recently rolled out to fix the problem in pulling the manifest from luarocks.org, but this doesn't appear to be in the docker image.

How was luarocks pulling packages without curl or wget being present in the image, but now it needs them.

I've been looking through, kong/kong, kong/docker-kong, luarocks, luajit repos trying to pin it all together.

Any ideas?

[Water-Melon]

Hi @cuotos ,
It’s likely that LuaRocks is using curl or wget to download the dependencies.

When installing locally, did you only provide the .rockspec file, or is there also a .src.rock file?

LuaRocks 3.12.0 does fix this issue. If you need a temporary workaround, you can install LuaRocks 3.12.0 mannully on top of Kong’s base image.

As for the inconsistent errors between versions 3.9.0 and 3.9.1, I suspect it might be related to differences in the tools provided by the base image.

[cuotos]

I was just trying to knock up a Dockerfile to show it not working, but can't replicate, so clearly made a mistake somewhere in downloading / copying the rock files into the image to be installed by Luarocks. But that was only a secondary point anyway.

It’s likely that LuaRocks is using curl or wget to download the dependencies.

This is where my confusion comes from. in Kong:3.8.0 and 3.9.0 the Docker image does not contain curl or wget but Luarocks worked fine (until the oversized manifest issue). but Kong 3.9.1, Luarocks now does a check for curl or wget, but is using the same version of Luarocks (3.11.1). I really cant understand this change in behaviour, unless the 3.11.1 is not true and Kong has used a different version of luarocks between 3.9.0 and 3.9.1

3.9.0

1.320 Warning: Failed searching manifest: Failed loading manifest for https://luarocks.org: Error loading file: [string "/var/cache/luarocks/https___luarocks.org/mani..."]:203843: main function has more than 65536 constants

3.9.1

0.136 Warning: Failed searching manifest: Failed downloading https://luarocks.org/manifest-5.1 - no downloader tool available, please install wget or curl in your system