Skip to content

Commit bc2a82a

Browse files
committed
clearer instructions in README
1 parent b9b6229 commit bc2a82a

File tree

1 file changed

+17
-1
lines changed

1 file changed

+17
-1
lines changed

README.md

Lines changed: 17 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,17 @@
1-
Docker image registry for SWE-bench, created by [Epoch AI](https://epochai.org).
1+
This README describes the [Epoch AI](https://epoch.ai) Docker image registry for SWE-bench.
2+
3+
[registry_packages]: https://github.com/orgs/epoch-research/packages?repo_name=SWE-bench
4+
5+
# How to use our image registry
6+
Our [image registry][registry_packages] is public, MIT-licensed, and hosted on [GitHub Container Registry](https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry). Each image can be accessed by its name, and we follow the same naming pattern as the original SWE-bench authors. At the moment, all images only have the tag `latest`.
7+
8+
The naming format is `ghcr.io/epoch-research/swe-bench.eval.<arch>.<instance_id>`, for example `ghcr.io/epoch-research/swe-bench.eval.x86_64.astropy__astropy-13236`.
9+
10+
For `x86_64`, we're able to build 2290/2294 (99.8%) of the images, and all 500/500 out of the SWE-bench Verified set.
11+
12+
For `arm64`, 1819 (out of 2294) images are provided on a best-effort basis, and have not been tested.
13+
14+
15+
16+
# Launch blog post
17+
[How to run SWE-bench Verified in one hour on one machine](https://epoch.ai/blog/swebench-docker), Epoch AI blog

0 commit comments

Comments
 (0)