LuaJIT error on logs

[a3nick]

I receive an alert on the docker container log related to a LuaJIT issue, but the system seems to work correctly

docker 18.09.0 on raspbian 9.0 (armv7l - rPI)

nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:
        no field package.preload['resty.core']
        no file './resty/core.lua'
        no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua'
        no file '/usr/local/share/lua/5.1/resty/core.lua'
        no file '/usr/local/share/lua/5.1/resty/core/init.lua'
        no file '/usr/share/lua/5.1/resty/core.lua'
        no file '/usr/share/lua/5.1/resty/core/init.lua'
        no file '/usr/share/lua/common/resty/core.lua'
        no file '/usr/share/lua/common/resty/core/init.lua'
        no file './resty/core.so'
        no file '/usr/local/lib/lua/5.1/resty/core.so'
        no file '/usr/lib/lua/5.1/resty/core.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
        no file './resty.so'
        no file '/usr/local/lib/lua/5.1/resty.so'
        no file '/usr/lib/lua/5.1/resty.so'
        no file '/usr/local/lib/lua/5.1/loadall.so')

Thank you

[tcwx]

Same issue here
Docker version 18.09.6, build 481bc77
Ubuntu 18.04.2LTS

[j0nnymoe]

Please can you provide more information on how we can replicate this issue.

• Changes you've made to the config
• How you deployed the container (with commands)

[a3nick]

Please can you provide more information on how we can replicate this issue.

* Changes you've made to the config

* How you deployed the container (with commands)

I deployed the container using the following docker-compose file where i replaced sensitive data with [...]

version: "2"

services:
  gitea:
    image: kunde21/gitea-arm
    restart: always
    volumes:
      - ./gitea/data:/data
    ports:
      - "3000:3000"
      - "22:22"
  proxy:
    image: linuxserver/letsencrypt
    cap_add:
      - NET_ADMIN
    links:
      - "gitea"
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/London
      - URL=[...]
      - SUBDOMAINS=[...]
      - VALIDATION=http
      - EMAIL=[...]
      - ONLY_SUBDOMAINS=true
    volumes:
      - ./proxy/config:/config
    ports:
      - 443:443
      - 80:80
    restart: always

i haven't changed anything until the last update, this is the configuration file i added to nginx/site-confs folder

server {
    listen 443 ssl;
    server_name [...];
    location / {
            proxy_pass http://gitea:3000;
            proxy_set_header Host $http_host;
            proxy_set_header X-Forwarded-For $remote_addr;
            proxy_set_header X-Forwarded-Proto http;
            proxy_buffer_size   128k;
            proxy_buffers   4 256k;
            proxy_busy_buffers_size   256k;
            proxy_connect_timeout       300;
            proxy_send_timeout          300;
            proxy_read_timeout          300;
            send_timeout                300;
        }
}

[aptalca]

Reproduced the issue, looking into it.

Thanks

[sparklyballs]

i don't think there's a simple fix for this as it stands.

openresty package that satisfies the warnings is a specific compile of nginx with different modules etc.

https://git.alpinelinux.org/aports/tree/testing/openresty/APKBUILD

[sparklyballs]

openresty added a check for this version with the nginx lua modules version 1.15 which was recently updated from .13 to fix problems in one of the armxx versions

[VirtualL]

Have the same issue:

.....
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:

no field package.preload['resty.core']
no file './resty/core.lua'
no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua'
no file '/usr/local/share/lua/5.1/resty/core.lua'
no file '/usr/local/share/lua/5.1/resty/core/init.lua'
no file '/usr/share/lua/5.1/resty/core.lua'
no file '/usr/share/lua/5.1/resty/core/init.lua'
no file '/usr/share/lua/common/resty/core.lua'
no file '/usr/share/lua/common/resty/core/init.lua'
no file './resty/core.so'
no file '/usr/local/lib/lua/5.1/resty/core.so'
no file '/usr/lib/lua/5.1/resty/core.so'
no file '/usr/local/lib/lua/5.1/loadall.so'
no file './resty.so'
no file '/usr/local/lib/lua/5.1/resty.so'
no file '/usr/lib/lua/5.1/resty.so'
no file '/usr/local/lib/lua/5.1/loadall.so')
Server ready

Runing on Unraid 6.7.0 ,Not getting this error in the previous version (not sure whitch one start this error , but was working ok 10 days ago+-)
Also, everything working good with this error. (No changes made in the config)

[ethanopp]

+1 causing my home-assistant reverse proxy to fail

[aptalca]

@ethanopp I highly doubt that. Reverse proxy shouldn't be relying on the lua module. Check your confs

[ethanopp]

Hmm alright I’ll check but didn’t change anything - just re-pulled and it was working fine before

UPDATE: @aptalca - disregard... other containers working, still getting that error though

[perfectly-preserved-pie]

Same here.
Ubuntu 18.04.2 LTS.
Running the container via Portainer.

Build date is BUILD_DATE=2019-05-10T09:17:08-04:00

nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)


nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:


	no field package.preload['resty.core']


	no file './resty/core.lua'


	no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua'


	no file '/usr/local/share/lua/5.1/resty/core.lua'


	no file '/usr/local/share/lua/5.1/resty/core/init.lua'


	no file '/usr/share/lua/5.1/resty/core.lua'


	no file '/usr/share/lua/5.1/resty/core/init.lua'


	no file '/usr/share/lua/common/resty/core.lua'


	no file '/usr/share/lua/common/resty/core/init.lua'


	no file './resty/core.so'


	no file '/usr/local/lib/lua/5.1/resty/core.so'


	no file '/usr/lib/lua/5.1/resty/core.so'


	no file '/usr/local/lib/lua/5.1/loadall.so'


	no file './resty.so'


	no file '/usr/local/lib/lua/5.1/resty.so'


	no file '/usr/lib/lua/5.1/resty.so'


	no file '/usr/local/lib/lua/5.1/loadall.so')

Server ready

[CHBMB]

AFAIUI we're dependent on an upstream fix for this @straying1 and it won't affect the workings of the container unless you're specifically using Lua

[perfectly-preserved-pie]

That's fine with me, thank you!

[tomraithel]

I have the same problem. How can I bypass this issue until a fix is provided? I´m currently testing the image on an Amazon EC2 instance with this params:

sudo docker run \
  --name=letsencrypt \
  --cap-add=NET_ADMIN \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/London \
  -e URL=foo.com \
  -e SUBDOMAINS=bla \
  -e VALIDATION=http \
  -e EMAIL=xxx@xxxx.com \
  -e DHLEVEL=2048 \
  -e ONLY_SUBDOMAINS=true \
  -p 443:443 \
  -p 80:80 \
  -v le-config:/config \
  --rm \
  -d \
  linuxserver/letsencrypt

Output in the error-logs is the same as described above. After that, the container shuts down.