← Directory

Folding@home

Folding@home is a distributed computing project for simulating protein dynamics, including the process of protein folding and the movements of proteins…

  • Home Automation
Folding@home is a distributed computing project for simulating protein dynamics, including the process of protein folding and the movements of proteins implicated in a variety of diseases. It brings together citizen scientists who volunteer to run simulations of protein dynamics on their personal computers. Insights from this data are helping scientists to better understand biology, and providing new opportunities for developing therapeutics.

Platform availability

Available on 1 of 6 install platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)

Also on Docker Hub

Health score

13/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
351 install platform, install notes, Docker image
Light to run
2032 GB minimum RAM, runs on ARM

Based on 3 of 4 factors.

How is this calculated?

A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.

Availability: platform listings confirmed today

No GitHub repository data collected yet.

Checked 9 days ago - source: GitHub (BigBearTechWorld/foldingathome)

Resources & Compatibility

Minimum requirements: 32 GB RAM, 10240 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 9 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set PUID/PGID to your host IDs Before starting, set PUID/PGID (the user and group IDs the container runs as) to your Linux user and group IDs, which you can check with `id your_user`. Without this, the container may not be allowed to read or write your files, causing permission errors. source
  • Open port 9117 for the web UI Map port 9117 to the container's port 9117 so you can open the app's settings page in a browser. If you forget this, the app may be running but you will not be able to reach its web interface. source
  • Keep the config folder safe Point the `/config` volume to a persistent folder on your machine, such as `/path/to/jackett/data:/config`. This folder stores the app's settings, so if it is deleted or not kept safe, you can lose your setup and have to start over. source

Fetched 8 days ago - each note links to its source

Alternatives (2)

  • Dockhand - Dockhand is a self-hosted, web-based Docker management platform that gives you a single dashboard to deploy containers, manage stacks, trac…
  • Portainer - Portainer is a lightweight, open-source container management UI for Docker, Swarm, Podman, and Kubernetes environments.

Checked 9 days ago - source: AlternativeTo

Common questions

Which Folding server URL should I use for a headless Linux Folding@home setup?

The headless Linux setup guidance covers which Folding server URLs to use for Folding@home clients 8.3 and 8.4.

Where should I post questions about running the linuxserver/foldingathome Docker image on Unraid?

Use the Unraid support thread for the linuxserver/foldingathome Docker image, where users post questions and issues about running the app.

Are Folding@home GPU problems often related to driver versions?

Many GPU problems appear to revolve around specific driver versions. Checking reports from other folding users can help, even though NVIDIA has its own support structure.

What should I check first when the Folding@home client misbehaves?

Check the client log first, because the answer is usually in the log when the client misbehaves. The troubleshooting page also covers the most common failure modes.

Answers sourced from foldingathome.org, forum.foldingathome.org, forum.foldingathome.org, forums.unraid.net

Community

Collected 4 days ago - public community threads