Added documentation for docker usage. #1067
Conversation
|
This looks good to me. And it reminds me that we really need to be able to tell the CLI to use a daemon running somewhere else. Would be cool if we could control an ipfs daemon running on a docker image in the same way docker works on OSX with boot2docker. |
mlovci
changed the title
| @@ -89,6 +89,53 @@ Basic proof of 'ipfs working' locally: | |||
| ipfs cat <that hash> | |||
|
|
|||
|
|
|||
| ### Docker usage | |||
|
|
|||
| An ipfs docker image is hosted at [hub.docker.com/u/jbenet/go-ipfs](hub.docker.com/u/jbenet/go-ipfs). | |||
There was a problem hiding this comment.
sorry, this image was outdated. I've updated that repo to point to https://github.com/ipfs/go-ipfs
(i wish i could get the dockerhub repo to be https://registry.hub.docker.com/repos/ipfs/ but someone owns it i think :/)
|
@mlovci thank you! this looks great! 👍 :) |
| @@ -89,6 +89,53 @@ Basic proof of 'ipfs working' locally: | |||
| ipfs cat <that hash> | |||
|
|
|||
|
|
|||
| ### Docker usage | |||
|
|
|||
| An ipfs docker image is hosted at [hub.docker.com/u/ipfs/go-ipfs](hub.docker.com/u/ipfs/go-ipfs). | |||
There was a problem hiding this comment.
@mlovci ah sorry, didnt mean to change it to this yet -- I dont have control of that account atm (only that i want to use it). will update when i get control
i did update https://registry.hub.docker.com/u/jbenet/go-ipfs/ to point to https://github.com/ipfs/go-ipfs/ (instead of https://github.com/jbenet/go-ipfs/)
|
I'll remove that commit |
|
@mlovci thanks!! 👍 |
Added documentation for docker usage.
Updated README.md to include instructions on how to start a
go-ipfsdocker container, connect to peers and add files to ipfs. (extra instructions for boot2docker vm too).Fix for #1052