go back to a named volume for containers

README.md

@@ -24,8 +24,8 @@ and group inside the container as I2P.
 
 When you run a reseed under Docker in this fashion, it will automatically
 generate a self-signed certificate for your reseed server in a Docker volume
-under your I2P directory. *Back up this directory*, if it is lost it is
-impossible to reproduce.
+mamed reseed-keys. *Back up this directory*, if it is lost it is impossible
+to reproduce.
 
 Please note that Docker is not currently compatible with .onion reseeds unless
 you pass the --network=host tag.
@@ -37,7 +37,7 @@ you pass the --network=host tag.
             --publish 443:8443 \
             --restart always \
             --volume $HOME/.i2p/netDb:$HOME/.i2p/netDb:z \
-            --volume $HOME/i2p/reseed-keys:/var/lib/i2p/i2p-config/reseed \
+            --volume reseed-keys:/var/lib/i2p/i2p-config/reseed \
             eyedeekay/reseed \
                 --signer $YOUR_EMAIL_HERE
 
@@ -50,7 +50,7 @@ you pass the --network=host tag.
             --publish 443:8443 \
             --restart always \
             --volume /PATH/TO/USER/I2P/HERE/netDb:/var/lib/i2p/i2p-config/netDb:z \
-            --volume /PATH/TO/USER/I2P/HERE/reseed-keys:/var/lib/i2p/i2p-config/reseed \
+            --volume reseed-keys:/var/lib/i2p/i2p-config/reseed \
             eyedeekay/reseed \
                 --signer $YOUR_EMAIL_HERE
 
@@ -68,7 +68,7 @@ work for you. In that case, just copy-and-paste:
             --publish 443:8443 \
             --restart always \
             --volume /var/lib/i2p/i2p-config/netDb:/var/lib/i2p/i2p-config/netDb:z \
-            --volume /var/lib/i2p/i2p-config/reseed-keys:/var/lib/i2p/i2p-config/reseed \
+            --volume reseed-keys:/var/lib/i2p/i2p-config/reseed \
             eyedeekay/reseed \
                 --signer $YOUR_EMAIL_HERE