I have encountered the following error in the crackq container log:
crackq | Traceback (most recent call last):
crackq | File "/usr/local/bin/rq", line 8, in
crackq | sys.exit(main())
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 829, in call
crackq | return self.main(args, kwargs)
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 782, in main
crackq | rv = self.invoke(ctx)
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 1259, in invoke
crackq | return _process_result(sub_ctx.command.invoke(sub_ctx))
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 1066, in invoke
crackq | return ctx.invoke(self.callback, ctx.params)
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 610, in invoke
crackq | return callback(args, kwargs)
crackq | File "/usr/local/lib/python3.6/dist-packages/rq/cli/cli.py", line 83, in wrapper
crackq | return ctx.invoke(func, cli_config, *args[1:], *kwargs)
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 610, in invoke
crackq | return callback(args, kwargs)
crackq | File "/usr/local/lib/python3.6/dist-packages/rq/cli/cli.py", line 220, in worker
crackq | settings = read_config_file(cli_config.config) if cli_config.config else {}
crackq | File "/usr/local/lib/python3.6/dist-packages/rq/cli/helpers.py", line 27, in read_config_file
crackq | settings = importlib.import_module(module)
crackq | File "/usr/lib/python3.6/importlib/init.py", line 126, in import_module
crackq | return _bootstrap._gcd_import(name[level:], package, level)
crackq | File "", line 994, in _gcd_import
crackq | File "", line 971, in _find_and_load
crackq | File "", line 953, in _find_and_load_unlocked
crackq | ModuleNotFoundError: No module named 'rq_settings'
This seems to come up on the:
docker-compose-opencl.yml
docker-compose-opencl.wldapserver.yml
docker-compose.test.yml
This Error doesnt show up on the dev.yml though.
It seems to be the case because the environment var 'PYTHONPATH' is on these leads to /opt/crackq/build/crackq and not /opt/crackq/build/
If u look inside the container the rq and init.py is indeed on the path /opt/crackq/build/
Hey,
I have encountered the following error in the crackq container log:
crackq | Traceback (most recent call last): crackq | File "/usr/local/bin/rq", line 8, in
crackq | sys.exit(main())
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 829, in call
crackq | return self.main(args, kwargs)
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 782, in main
crackq | rv = self.invoke(ctx)
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 1259, in invoke
crackq | return _process_result(sub_ctx.command.invoke(sub_ctx))
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 1066, in invoke
crackq | return ctx.invoke(self.callback, ctx.params)
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 610, in invoke
crackq | return callback(args, kwargs)
crackq | File "/usr/local/lib/python3.6/dist-packages/rq/cli/cli.py", line 83, in wrapper
crackq | return ctx.invoke(func, cli_config, *args[1:], *kwargs)
crackq | File "/usr/local/lib/python3.6/dist-packages/click/core.py", line 610, in invoke
crackq | return callback(args, kwargs)
crackq | File "/usr/local/lib/python3.6/dist-packages/rq/cli/cli.py", line 220, in worker
crackq | settings = read_config_file(cli_config.config) if cli_config.config else {}
crackq | File "/usr/local/lib/python3.6/dist-packages/rq/cli/helpers.py", line 27, in read_config_file
crackq | settings = importlib.import_module(module)
crackq | File "/usr/lib/python3.6/importlib/init.py", line 126, in import_module
crackq | return _bootstrap._gcd_import(name[level:], package, level)
crackq | File "", line 994, in _gcd_import
crackq | File "", line 971, in _find_and_load
crackq | File "", line 953, in _find_and_load_unlocked
crackq | ModuleNotFoundError: No module named 'rq_settings'
This seems to come up on the:
This Error doesnt show up on the dev.yml though. It seems to be the case because the environment var 'PYTHONPATH' is on these leads to
/opt/crackq/build/crackqand not/opt/crackq/build/If u look inside the container the rq and init.py is indeed on the path/opt/crackq/build/I'll create a pull request to fix this :)