Lab41 / attalos

Joint Vector Spaces

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Error when running DenseCap in Dockerfile.torch container

agude opened this issue · comments

I get the following error on a51 when running DenseCap:

root@67c8667eda84:/densecap/densecap# th run_model.lua -input_image imgs/elephant.jpg
/root/torch/install/bin/luajit: /root/torch/install/share/lua/5.1/trepl/init.lua:384: /root/torch/install/share/lua/5.1/trepl/init.lua:384: /root/torch/install/share/lua/5.1/trepl/init.lua:384: /root/torch/install/share/lua/5.1/trepl/init.lua:384: /root/torch/install/share/lua/5.1/trepl/init.lua:384: module 'libcustn' not found:No LuaRocks module found for libcustn
    no field package.preload['libcustn']
    no file '/root/.luarocks/share/lua/5.1/libcustn.lua'
    no file '/root/.luarocks/share/lua/5.1/libcustn/init.lua'
    no file '/root/torch/install/share/lua/5.1/libcustn.lua'
    no file '/root/torch/install/share/lua/5.1/libcustn/init.lua'
    no file './libcustn.lua'
    no file '/root/torch/install/share/luajit-2.1.0-beta1/libcustn.lua'
    no file '/usr/local/share/lua/5.1/libcustn.lua'
    no file '/usr/local/share/lua/5.1/libcustn/init.lua'
    no file '/root/.luarocks/lib/lua/5.1/libcustn.so'
    no file '/root/torch/install/lib/lua/5.1/libcustn.so'
    no file '/root/torch/install/lib/libcustn.so'
    no file './libcustn.so'
    no file '/usr/local/lib/lua/5.1/libcustn.so'
    no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
    [C]: in function 'error'
    /root/torch/install/share/lua/5.1/trepl/init.lua:384: in function 'require'
    run_model.lua:5: in main chunk
    [C]: in function 'dofile'
    /root/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:145: in main chunk
    [C]: at 0x00406670
root@67c8667eda84:/densecap/densecap# exit
make: *** [attalos-torch] Error 1

This error did not happen before #74.

hey, did you solve the problem?

@puddinord We "worked around it" but never figured out the exact cause. We believe it was related to the specific hardware we were running on as it only manifested on one machine (with divergent hardware from the rest of our servers). Sorry I can't be more helpful. :-/