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

Dockerfile.minerva currently produces a bad image #12

Open
kltm opened this issue Nov 1, 2024 · 2 comments
Open

Dockerfile.minerva currently produces a bad image #12

kltm opened this issue Nov 1, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@kltm
Copy link
Member

kltm commented Nov 1, 2024

In geneontology/minerva:v4:

bash-4.4$ /app/run.sh 
bash: /app/run.sh: /bin/bash\nset: bad interpreter: No such file or directory
bash-4.4$ 
@kltm kltm added the bug Something isn't working label Nov 1, 2024
@kltm kltm moved this to In Progress in Noctua in AWS Nov 1, 2024
@kltm
Copy link
Member Author

kltm commented Nov 1, 2024

Tagging @mugitty

@kltm kltm closed this as completed Nov 2, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Noctua in AWS Nov 2, 2024
@kltm kltm reopened this Nov 4, 2024
@kltm
Copy link
Member Author

kltm commented Nov 4, 2024

It seems like we are now having issues with the minerva runner image taking 2GB only.
I'm not sure how this even worked, but I'm guessing that the previous version of the script didn't pass in the variable somehow and the default java value was used. Now that the script was fixed, it is using the explicit 2GB, which causes a heap error pretty quickly. We need to set this up to use the available memory (which I believe was 24GB).

@kltm kltm moved this from Done to In Progress in Noctua in AWS Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: In Progress
Development

No branches or pull requests

1 participant