Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
A
Alphafold3
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
RC Data Science
community-containers
Alphafold3
Commits
33f2d70e
Commit
33f2d70e
authored
2 months ago
by
Fortune Iriaye
Browse files
Options
Downloads
Patches
Plain Diff
Update Dockerfile
parent
6166cdc0
No related branches found
No related tags found
No related merge requests found
Pipeline
#13532
passed with stage
in 25 minutes and 1 second
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docker/Dockerfile
+7
-3
7 additions, 3 deletions
docker/Dockerfile
with
7 additions
and
3 deletions
docker/Dockerfile
+
7
−
3
View file @
33f2d70e
...
...
@@ -32,7 +32,8 @@ ENV PATH="/hmmer/bin:/alphafold3_venv/bin:$PATH"
RUN
pip3
install
--upgrade
pip
# Install HMMER. Do so before copying the source code, so that docker can cache
# the image layer containing HMMER.
# the image layer containing HMMER. Alternatively, you could also install it
# using `apt-get install hmmer` instead of bulding it from source.
RUN
mkdir
/hmmer_build /hmmer
;
\
wget http://eddylab.org/software/hmmer/hmmer-3.4.tar.gz
--directory-prefix
/hmmer_build
;
\
(
cd
/hmmer_build
&&
tar
zxf hmmer-3.4.tar.gz
&&
rm
hmmer-3.4.tar.gz
)
;
\
...
...
@@ -55,10 +56,13 @@ RUN build_data
# To work around a known XLA issue causing the compilation time to greatly
# increase, the following environment variable setting XLA flags must be enabled
# when running AlphaFold 3:
# when running AlphaFold 3. Note that if using CUDA capability 7 GPUs, it is
# necessary to set the following XLA_FLAGS value instead:
# ENV XLA_FLAGS="--xla_disable_hlo_passes=custom-kernel-fusion-rewriter"
# (no need to disable gemm in that case as it is not supported for such GPU).
ENV
XLA_FLAGS="--xla_gpu_enable_triton_gemm=false"
# Memory settings used for folding up to 5,120 tokens on A100 80 GB.
ENV
XLA_PYTHON_CLIENT_PREALLOCATE=true
ENV
XLA_CLIENT_MEM_FRACTION=0.95
ENTRYPOINT
["python3", "run_alphafold.py"]
\ No newline at end of file
CMD
["python3", "run_alphafold.py"]
\ No newline at end of file
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment