Running docker image outputs "Error running securify." on macOS #69
Labels
Comments
mihairaulea
changed the title
mihairaulea
changed the title
|
Hi @mihairaulea , thanks for the report! Unfortunately I cannot reproduce this with the latest commit on the master branch, are you using the commit b54522e as I am? |
|
Hi @hiqua , yes, i am. Cloned the repo yesterday. While building the image yesterday, had some issues(downloading soufle and other binaries), had to issue the command 3 times before a successful run. |
|
Okay, run with verbose. |
|
How much memory do you have on your computer? |
|
Also, |
|
It seems the I have 16GB, should be enough :) Also, ran with |
|
Yes, I meant that it is included in the Dockerfile so you shouldn't have to do anything in particular. Did you also try without |
|
Yes, tried without, as well. |
|
What is the RAM consumption at its peak? |
|
Maybe you can tell me more about the issues you had while building? Was it a network problem? Everything is downloaded from github, which is obviously not 100% resilient but you would have been quite unlucky to encounter issues right at that moment. What is the full |
|
Yep, network problem when building the image, but it never happened again. Here is the output of running the docker image, with -v. |
|
I bet you have a memory leak, investigating. |
|
Modified project.py, allocated 4GB of heap memory(hardcoded). Line 79 in project.py
Here is the output now: |
|
It's very possible that there's a memory leak (actually I'd be surprised if there isn't any!), but I still don't understand why I cannot reproduce this. How big is your swap partition? I have 16GB of memory and my swap is 16GB. |
|
Try with |
|
I ran your command, but I still cannot reproduce your bug after building the image from scratch. It runs fine with 11GB available in memory, and an empty swap. |
|
@mihairaulea I have met the same issue, do you have any new discoveries? |
|
I am experiencing the same issue: |
|
@aabdulwahed you're using macOS right? And @charles-lei as well? I don't, so that could explain why I cannot reproduce it. I'm not sure what the root issue is for now though. |
|
yes, I'm using macOS and docker toolbox |
|
Thanks @hiqua for swift reply, yes I am using MacOS.. Does it work for Ubuntu 18.04 LTS ? |
|
@aabdulwahed it works for me on Debian, I assume it will work on Ubuntu as well. It really seems to be related to macOS or at least to Docker on macOS. |
|
@hiqua thanks, I will move to Ubuntu |
|
Seems to be related to MacOS, specifically Mojave. okay, will run in a vm. |
|
Same here. Mac Os Mojave: 10.14 |
|
Ditto Truffle: 5.0.1 |
|
If those having problems with macOS can try with a VM on Ubuntu and see whether they have the same problems, that'd be great! So far I haven't seen anyone claiming that they could reproduce this issue on an OS different from macOS. |
hiqua
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using a macOS Mojave. Docker is up to date.
➜ ~ docker version
Client: Docker Engine - Community
Version: 18.09.0
API version: 1.39
Go version: go1.10.4
Git commit: 4d60db4
Built: Wed Nov 7 00:47:43 2018
OS/Arch: darwin/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 18.09.0
API version: 1.39 (minimum version 1.12)
Go version: go1.10.4
Git commit: 4d60db4
Built: Wed Nov 7 00:55:00 2018
OS/Arch: linux/amd64
Experimental: true
I have cloned the securify git repository, and ran
docker build . -t securifysuccessfully. I have checked that the Docker image was built, and is available.When running
docker run securifyas per the project documentation, i getRunning with a mounted volume yields the same output. I am confident the volume had only one contract in it, which was successfully analyzed with other engines.
The text was updated successfully, but these errors were encountered: