mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-11-06 20:17:38 +01:00
Merge branch 'master' of https://github.com/seaweedfs/seaweedfs.wiki
commit
c3258377e6
2 files changed
+3
-2
No files matched your search
+2
-2
@@ -175,14 +175,14 @@ docker build -f Dockerfile.local --no-cache -t localregistry/seaweedfs .
|
||||
You can use docker volumes to persist data:
|
||||
```bash
|
||||
# start our weed server daemonized
|
||||
docker run --name weed -d -p 9333:9333 -p 8080:8080 -p 18080:8080 \
|
||||
docker run --name weed -d -p 9333:9333 -p 8080:8080 -p 18080:18080 \
|
||||
-v seaweedvolume:/data chrislusf/seaweedfs server -dir="/data"
|
||||
```
|
||||
|
||||
Alternatively, you can mount a directory on the host machine into the container:
|
||||
```bash
|
||||
# start our weed server daemonized
|
||||
docker run --name weed -d -p 9333:9333 -p 8080:8080 -p 18080:8080 \
|
||||
docker run --name weed -d -p 9333:9333 -p 8080:8080 -p 18080:18080 \
|
||||
-v /opt/weedfs/data:/data chrislusf/seaweedfs server -dir="/data"
|
||||
```
|
||||
Note that according to [Docker's documentation](https://docs.docker.com/storage/volumes/), volumes are the preferred mechanism for persisting data.
|
||||
|
||||
@@ -73,6 +73,7 @@ s3.path-style-access=true
|
||||
s3.signer-type=AwsS3V4Signer
|
||||
s3.aws-access-key=YOUR_ACCESS_KEY
|
||||
s3.aws-secret-key=YOUR_SECRET_KEY
|
||||
s3.region=us-east-1
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
Reference in new issue
Block a user