-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dev/orch dapp walkthrough documentation #1169
base: main
Are you sure you want to change the base?
Changes from 1 commit
081e58a
4ca2cf7
18c0542
66d1615
7b9b1be
88f835f
3c549f7
c38f9ea
df834f3
5319631
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -8,6 +8,9 @@ Here, we will walk through installing the Orchestration-Basics demo project onto | |||||
- [Setting Up the Local Environment](#setting-up-the-local-environment) | ||||||
- [Overriding the Chain Registry for use with `agoric-sdk/multichain-testing`](#overriding-the-chain-registry-for-use-with-agoric-sdkmultichain-testing) | ||||||
- [Multichain-Testing Makefile Helpers](#multichain-testing-makefile-helpers) | ||||||
- [Troubleshooting Docker](#troubleshooting-docker) | ||||||
- [Disable Kubernetes](#disable-kubernetes) | ||||||
- [Increasing resources allocated to docker](#increasing-resources-allocated-to-docker) | ||||||
- [Adding a New Address](#adding-a-new-address) | ||||||
- [Funding the Account](#funding-the-account) | ||||||
- [Building \& Deploying the dApp](#building--deploying-the-dapp) | ||||||
|
@@ -106,6 +109,19 @@ If you need to restart your environment for any reason, use the following comman | |||||
make teardown ; make stop; make stop-forward; make clean; make; make port-forward | ||||||
``` | ||||||
|
||||||
## Troubleshooting Docker | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is absolutely necessary - thanks for doing this! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can probably have a separate page for troubleshooting and not just for Docker, that can be updated more frequently than this page? What are your thoughts on this? @Jovonni |
||||||
During setting up the environment, you may run into a few issues with docker. Here are two common setup requirements. | ||||||
|
||||||
### Disable Kubernetes | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I thought we have to enable it, not disable it. That's what I had to do. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also, we should recommend somewhere to click the "reset k8s cluster" button before spinning it up |
||||||
Inside of "settings", navigate to the "kubernetes" section. Here, you want to ensure that you deselect the "Enable Kubernetes" checkbox | ||||||
<img src="../../assets/docker-kube.png" width="100%" /> | ||||||
|
||||||
### Increasing resources allocated to docker | ||||||
From inside of "settings", navigate to the "Resources" section. By default docker doesn't optimize the resources allocated for running resource-intensive environments. For this environment, we want to ensure our `CPU limit`, `Memory Limit`, and `Swap` are all bumped up to 75% their max. You can always increase/decrease after you get everything setup, and determine how much resources are needed for your machine. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the % depends on your machine. For me, 10GB memory worked, while 8GB did not. My swap was at 1GB in both cases. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I also think this number will be different for different people. I had to bump up my memory to 15GB for the pods to be up and running under 15 minutes.
Suggested change
|
||||||
|
||||||
<img src="../../assets/docker-resources.png" width="100%" /> | ||||||
|
||||||
|
||||||
## Adding a New Address | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A line or two about the reasoning behind would be very appreciated by devs IMO. To answer questions like: why are we doing this? what/where is this new address needed for? |
||||||
|
||||||
Before deploying the contract, we want to generate a new address using the keyring inside of the localchain environment. To add a new address to the keychain inside the Kubernetes pod, run the following command from the top-level directory: | ||||||
|
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.
a) targets are run sequentially afaik so we can use it like this
b) better yet, thoughts on adding a restart target in the Makefile helpers above?
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.
makes sense to me.