This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Add update service node page for docker in Lisk Service v0.7.0 #1850
There are no files selected for viewing
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -11,11 +11,24 @@ Mona Bärenfänger <[email protected]> | |
| :url_FLUSHALL: https://redis.io/commands/FLUSHALL | ||
| :url_snapshot_config: configuration/index.adoc | ||
| :url_backups: management/snapshots.adoc | ||
| :url_rel_notes: https://github.com/LiskHQ/lisk-service/releases/ | ||
|
|
||
|
|
||
| == Build Docker image | ||
|
|
||
| .Inside the lisk-service root folder | ||
| ---- | ||
| make build | ||
| ---- | ||
| This creates the necessary Docker images to start Lisk Service in the containers. | ||
|
|
||
| == Start | ||
|
|
||
| .Inside the lisk-service root folder | ||
| ---- | ||
| cp ./docker/example.env .env | ||
| ---- | ||
| ---- | ||
| make up | ||
| ---- | ||
|
|
||
|
|
@@ -204,10 +217,126 @@ If you wish to take a snapshot of your Docker installation, the details can be f | |
|
|
||
| == Logging | ||
|
|
||
| The possibility exists here to either use the `docker` commands or the `make` commands to check the logs, and both options are listed here below. | ||
|
|
||
| For `docker`, to check the logs for the different microservices of Lisk Service, use the command `docker container logs CONTAINER`, where `CONTAINER` is the respective Docker container that holds the logs you wish to view. | ||
|
|
||
| For example, to see the logs for the Gateway microservice, execute the following command: | ||
|
|
||
| ---- | ||
| docker container logs lisk-service_gateway_1 | ||
| ---- | ||
|
|
||
| To check the logs for different microservices using the `make` commands, the following commands listed below can be used: | ||
|
|
||
| .Displays the logs for all the microservices that have been logged so far, and that are currently existing | ||
| ---- | ||
| make logs | ||
| ---- | ||
|
|
||
| .Displays the latest logs for all the microservices | ||
| ---- | ||
| make logs-live | ||
| ---- | ||
|
|
||
| .Displays the logs for the specified microservice. | ||
| ---- | ||
| make logs-blockchain-connector | ||
| ---- | ||
| In the above example, it will display logs only for the `blockchain-connector` microservice. | ||
|
|
||
| .Displays the latest logs for the specified microservice. | ||
| ---- | ||
| make logs-live-blockchain-connector | ||
| ---- | ||
| In the above example, it will display latest logs only for the `blockchain-connector` microservice. | ||
|
|
||
|
|
||
| Replace the `blockchain-connector` with the specific service name required. | ||
|
|
||
|
|
||
| == Upgrade Lisk Service | ||
|
|
||
| To upgrade the Docker container to a desired version, please follow one of the two options below. | ||
chris529 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| ==== Option A - Download pre-built images from DockerHub | ||
|
There was a problem hiding this comment. Option A should be the recommended way to upgrade Lisk Service, imho Option A and B should be switched, because B looks easier There was a problem hiding this comment. Also, imho it would be nice to use tabs to switch between Option A & B There was a problem hiding this comment. OK, I have now added tabs. There was a problem hiding this comment.
I'd prefer that |
||
|
|
||
| . Update `docker-compose.yml` to download the specific image versions from the DockerHub as shown below. Update the `0.7.0` tag against the specified images with the desired version. | ||
chris529 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| + | ||
| ---- | ||
chris529 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| blockchain-app-registry: | ||
| image: lisk/service_blockchain_app_registry:0.7.0 | ||
| ... | ||
|
|
||
| blockchain-connector: | ||
| image: lisk/service_blockchain_connector:0.7.0 | ||
| ... | ||
|
|
||
| blockchain-indexer: | ||
| image: lisk/service_blockchain_indexer:0.7.0 | ||
| ... | ||
|
|
||
| blockchain-coordinator: | ||
| image: lisk/service_blockchain_coordinator:0.7.0 | ||
| ... | ||
|
|
||
| transaction-statistics: | ||
| image: lisk/service_transaction_statistics:0.7.0 | ||
| ... | ||
|
|
||
| fee-estimator: | ||
| image: lisk/service_fee_estimator:0.7.0 | ||
| ... | ||
|
|
||
| gateway: | ||
| image: lisk/service_gateway:0.7.0 | ||
| ... | ||
|
|
||
| market: | ||
| image: lisk/service_market:0.7.0 | ||
| ... | ||
|
|
||
| export: | ||
| image: lisk/service_export:0.7.0 | ||
|
|
||
| ---- | ||
|
|
||
| . Stop Lisk Service | ||
| + | ||
| ---- | ||
| make stop | ||
| ---- | ||
| NOTE: In case the database needs to be flushed please execute the `make down` command instead. Please check the {url_rel_notes}[release notes] for the relevant version to see if the existing databases need to be flushed. | ||
chris529 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| . Start Lisk Service in the containers. | ||
| + | ||
| ---- | ||
| make up | ||
| ---- | ||
|
|
||
|
|
||
| ==== Option B - Build images locally | ||
|
|
||
| Build the images locally using the following steps. | ||
|
There was a problem hiding this comment. At what point does it describe how to download and install the new version? There was a problem hiding this comment. Seems like the step to run There was a problem hiding this comment. Done as suggested 👍 |
||
| Navigate inside the lisk-service root folder, and execute the following commands. | ||
|
|
||
| . Stop Lisk Service | ||
| + | ||
| ---- | ||
| make stop | ||
| ---- | ||
| NOTE: In case the database needs to be flushed please execute the `make down` command instead. Please check the {url_rel_notes}[release notes] for the relevant version to see if the existing databases need to be flushed. | ||
|
|
||
| . Build the required updated Docker images. | ||
| + | ||
| ---- | ||
| make build | ||
| ---- | ||
|
|
||
| . Start Lisk Service in the containers. | ||
chris529 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| + | ||
| ---- | ||
| make up | ||
| ---- | ||
|
|
||
| To verify the microservice logs, please refer to the <<Logging>> section. | ||
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -10,6 +10,7 @@ Mona Bärenfänger <[email protected]> Muhammad Talha <muhammad.talha@lightcurv | |
| // External URLs | ||
| :url_pm2_docs: https://pm2.keymetrics.io/docs/usage/quick-start/ | ||
| :url_FLUSHALL: https://redis.io/commands/FLUSHALL | ||
| :url_pm2_management: https://pm2.keymetrics.io/docs/usage/log-management/ | ||
| :url_backups: management/snapshots.adoc | ||
|
|
||
| //TODO: add in link to new Backups page for importing the DB snapshot manually | ||
|
|
@@ -103,6 +104,7 @@ Alternatively, it is also possible to check the logs for a specific PM2 process | |
| For example, `pm2 logs 0` can be used to check the Lisk Service Gateway logs. | ||
|
|
||
| TIP: The process ID of each PM2-managed process can be seen by executing the <<list>> command. | ||
| To learn more about PM2 log management please refer the {url_pm2_management}[PM2 logs documentation]. | ||
|
|
||
| For example, to see the logs for the Gateway microservice, execute the following command: | ||
|
|
||
|
|
||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't think this needs t be done every time Lisk Service is started, so it doesn't really fit here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see your point Mona...I checked with @nagdahimanshu earlier, and he recommends that we should leave it here as it can be beneficial when Lisk Service is started for the first time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but this is not about starting it for the first time, it is about how to start it in general. I don't think you need to do it every time you start Lisk Service. So it shouldn't be mentioned here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We advice that the user performs this step (sets the
.envfile for all the necessary environment variable configuration) when starting the Lisk Service on with Docker Compose for the first time. Alternatively, they canexportthe necessary environment variables on the terminal before starting the containers which can be quite cumbersome.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As mentioned, this is not about starting for the first time. This step is already included at the right location, which is the setup guides: https://liskhq.github.io/lisk-docs/lisk-service/0.7/setup/docker.html#connecting-lisk-service-to-a-blockchain-node
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This section is about managing the Lisk Service docker setup. So, I think, it is relevant to maintain the necessary environment variables with the
.envfile. Alternatively, users canexportthe native environment variables which could be quite messy and inconvenient. If you prefer not having it here, you can remove the section but share a link on how to maintain the necessary environment variable information.