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-compose run db-setup XXX fails due to no space left on device #92

Open
JackKay404 opened this issue Jul 25, 2024 · 0 comments
Open

Comments

@JackKay404
Copy link

When running the automatic database setup using docker-compose run db-setup as in the README.md the download is terminated prematurely with some text output stating for ecample:

Cannot write to '/tmp/12645459548716115717/highquality_clust30_ca' (No space left on device).

This is caused because the download script stores files in the /tmp directory of the container and docker's default maximum tmpfs size being 50 % of the RAM available on the host machine (which in my case was 32 G).

As stated in the docker documentation when using docker run you can control the upper limit of the tmpfs mount using the --tmpfs-size option however in docker-compose this can be set like:

tmpfs:
      - /tmp:exec,size=200G

This however did not work for me, the container crashed every time I tried. Instead the workaround I used was to simply change the directory the downloads were sent to from /tmp to /downloads, lines 11 and 15 of setup_db.sh
setup_db.sh Line 11

    "${APP}" databases "${DB}" "/opt/mmseqs-web/databases/${SAFE}" /downloads || continue

setup_db.sh Line 15

    "${APP}" createindex "/opt/mmseqs-web/databases/${SAFE}" /downloads --split 1

Maybe someone else has a more elegant solution?

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

1 participant