Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docker failing to run #31

Open
enzok opened this issue Jan 27, 2021 · 3 comments
Open

docker failing to run #31

enzok opened this issue Jan 27, 2021 · 3 comments

Comments

@enzok
Copy link

enzok commented Jan 27, 2021

Ubuntu 20.04 (latest updates)
docker 19.03.8
any xls or doc file

Was working in early January.
Sits over 5 minutes on 'Checking for ViperMonkey and dependency updates...'

sudo ViperMonkey/docker/dockermonkey.sh bad4.xls
[] Running 'docker ps' to see if script has required privileges to run...
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
02b0dd08a6ae haroldogden/vipermonkey:latest "bash" 58 seconds ago Up 57 seconds hopeful_margulis
d9ce0e7520b8 haroldogden/vipermonkey:latest "bash" 8 minutes ago Up 8 minutes practical_mccarthy
[+] Other ViperMonkey containers are running!
[
] Pulling and starting container...
latest: Pulling from haroldogden/vipermonkey
Digest: sha256:433c88f2ff925f33d38486f394c069f6d16ca0172ef5a2d9a063192604f98e5a
Status: Image is up to date for haroldogden/vipermonkey:latest
docker.io/haroldogden/vipermonkey:latest
[] Attempting to copy file bad4.xls into container ID aa8c3679061be39cf523a11ec3664d7b26f9fb9fcf95843f0ecebb46f8fbf3f8
[
] Starting openoffice listener for file content conversions...
[] Checking for ViperMonkey and dependency updates...
[
] Disabling network connection for container ID aa8c3679061be39cf523a11ec3664d7b26f9fb9fcf95843f0ecebb46f8fbf3f8
Usage: vmonkey.py [options] [filename2 ...]


| | / ()__ ___ / |/ / ____ / /___ __ __
| | / / / __ / _ / / /|/ / __ / __ / /// _ / / / /
| |/ / / /
/ / / / / / / / // / / / / ,< / __/ // /
|
// ./_// // //_// ///||___/_, /
// /___/
vmonkey 0.08 - https://github.com/decalage2/ViperMonkey
THIS IS WORK IN PROGRESS - Check updates regularly!
Please report any issue at https://github.com/decalage2/ViperMonkey/issues

vmonkey.py: error: no such option: --jit
[*] Done - Killing docker container aa8c3679061be39cf523a11ec3664d7b26f9fb9fcf95843f0ecebb46f8fbf3f8

@chezwicker
Copy link

Have a look at the PR I submitted, with that you can use a docker image built directly from the current version of the code. The problem with --jit missing is that the docker image referenced from dockermonkey.sh is too old.

@kirk-sayre-work
Copy link
Owner

Hmm, that's weird. the dockermonkey.sh script does a "git pull" on the ViperMonkey repo before running the analysis, so it should have the up to date version. Let me look some more at this.

@enzok
Copy link
Author

enzok commented Mar 2, 2021

Seems to only run for me, if I su to root. But I know prior to encountering this error I was running as non-root.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants