From ff20ce46cb8ceb50af6d55a20206962ac3292e74 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Sun, 31 Oct 2021 21:20:30 -0700 Subject: [PATCH] Updated Docker Image Registry with SeaweedFS (markdown) --- Docker-Image-Registry-with-SeaweedFS.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Docker-Image-Registry-with-SeaweedFS.md b/Docker-Image-Registry-with-SeaweedFS.md index b2c651a..74e8ba5 100644 --- a/Docker-Image-Registry-with-SeaweedFS.md +++ b/Docker-Image-Registry-with-SeaweedFS.md @@ -7,7 +7,7 @@ There are two ways to use SeaweedFS as a storage backend: For better performance, using S3 API is recommended. This is because FUSE mount currently needs to save the file to a local folder, before uploading the file to SeaweedFS cluster. # Configure Registry to use SeaweedFS S3 -Here is an example registry configuration. If you have checked out https://github.com/distribution/distribution, save this file as `cmd/registry/config-seaweedfs.yml`. +Assuming SeaweedFS S3 API is on `192.168.2.4:8333`, here is an example registry configuration. If you have checked out https://github.com/distribution/distribution, save this file as `cmd/registry/config-seaweedfs.yml`. ``` version: 0.1