-
Notifications
You must be signed in to change notification settings - Fork 32
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
makeReport issue, docker container crash #105
Comments
Hi, how large are your input samples? And are you running this on a laptop do you have plenty of disk space? How are you allocating the 60gb memory have you increase the memory available in docker settings as well as the workflow for this process? Although i would not have thought 60gb memory is required for the make report process |
hi @sarahjeeeze , |
Could you share the |
|
in the settings of the app have you also increased the docker memory allowance to 60gb? 125 is usually the container failing to execute. |
We have an update coming to the workflow this Wednesday which should reduce to memory required by the report step considerably which will hopefully fix this issue. |
Operating System
Ubuntu 22.04
Other Linux
No response
Workflow Version
v1.2.1
Workflow Execution
EPI2ME Desktop (Local)
Other workflow execution
No response
EPI2ME Version
v5.1.14
CLI command run
No response
Workflow Execution - CLI Execution Profile
None
What happened?
6 samples across 2 PromethION runs, as I reported earlier. This time on Ubuntu 22.04, I allocated 60 GB of memory to the makereport process, but it couldn’t complete and caused Docker to crash.
Relevant log output
Application activity log entry
No response
Were you able to successfully run the latest version of the workflow with the demo data?
yes
Other demo data information
No response
The text was updated successfully, but these errors were encountered: