Add an explanation for managing data persistent #1503
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HoOngEe
force-pushed
the
feature/made-docker-image-data-persistent
branch
from
2b5717a to
a552e36
Compare
HoOngEe
force-pushed
the
feature/made-docker-image-data-persistent
branch
from
a552e36 to
434b002
Compare
ScarletBlue
suggested changes
May 9, 2019
README.md
Outdated
| @@ -53,6 +53,23 @@ docker run -it codechain-io/codechain:branch_or_tag_name | |||
|
|
|||
| This should result in CodeChain running. | |||
|
|
|||
| #### Making local database and keys persistent | |||
|
|
|||
| CodeChain depends on the local database and keys commonly stored under the directories `keys` and `db`. A Docker container is independent of host environment and other Docker images. Therefore, in case of running a new Docker container with an image with a new CodeChain version or even with the same image, the database and keys are not persistent. To solve the problem, one can take advantage of Docker's volume option. With the command below, | |||
There was a problem hiding this comment.
CodeChain depends on the local database and keys commonly stored under the directories keys and db. A Docker container is independent of host environment and other Docker images. Therefore, when running a new Docker container with an image with a new CodeChain version or even with the same image, the database and keys are not persistent. To solve the problem, one can take advantage of the Docker's volume option. With the command below,
HoOngEe
force-pushed
the
feature/made-docker-image-data-persistent
branch
from
434b002 to
df369ab
Compare
ScarletBlue
previously approved these changes
May 14, 2019
|
@HoOngEe Please resolve the conflicts |
HoOngEe
force-pushed
the
feature/made-docker-image-data-persistent
branch
from
9368ce8 to
145ef09
Compare
|
I resolved the conflicts |
sgkim126
requested changes
May 22, 2019
HoOngEe
force-pushed
the
feature/made-docker-image-data-persistent
branch
from
145ef09 to
53362f7
Compare
sgkim126
approved these changes
May 23, 2019
HoOngEe
force-pushed
the
feature/made-docker-image-data-persistent
branch
from
53362f7 to
00e675c
Compare
|
@sgkim126 I applied your suggestion and now the commit looks clear. |
Added an explanation in the `Setup > Using Docker` section.
HoOngEe
force-pushed
the
feature/made-docker-image-data-persistent
branch
from
810c3db to
d513a29
Compare
sgkim126
approved these changes
May 23, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should be merged after the #1499 is merged
It closes #720