-
Notifications
You must be signed in to change notification settings - Fork 99
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
feat: add containerized localnet #439
Conversation
this script is no longer working and has been deprecated by scripts/localnet.sh
- change to use bash script instead of sh to allow more refined syntax - set archwayd process to listen all addresses instead of localhost - set BINARY path dependent on whether using containers or local
- use image based on TAG env variable, make file will set the tag automatically - enable 26656 also - change to use the new scripts path
- Update image version to alpine 3.18 - rename the debug image to dev - add bash and jq for dev purposes
21a1999
to
13dbe6b
Compare
13dbe6b
to
8983aa4
Compare
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.
ran with the following diff
diff --git a/docker-compose.yaml b/docker-compose.yaml
index ab781ee..78cd0df 100644
--- a/docker-compose.yaml
+++ b/docker-compose.yaml
@@ -3,7 +3,7 @@ version: "3"
services:
node:
- image: ghcr.io/archway-network/archwayd-dev:${TAG}
+ image: ghcr.io/archway-network/archwayd-debug:latest
entrypoint:
- sh
- /opt/localnet.sh
and got the following error
❯ make localnet
# TAG=v4.0.0 docker-compose up
docker-compose up
WARN[0000] The "CONTINUE" variable is not set. Defaulting to a blank string.
[+] Running 0/1
⠿ node Error 1.2s
Error response from daemon: manifest unknown
make: *** [localnet] Error 18
How can I test this flow?
Note! that to test this out you need to change the |
Test and it works. Lets also please add docs to README.md to explain various methods of running the local networks |
5e41b18
to
f3bb272
Compare
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.
lgtm
Currently users are not able to run their Archway localnet in containers by using
docker-compose
This PR will propose the following changes to fix these issues:
make localnet
to start the containerized localnet with latest tagged image.make localnet-continue
to start the shutdownarchway-node-1
containerarchwayd-dev
instead ofarchwayd-debug
jq
andbash
which are used in thelocalnet.sh
scriptalpine:3.18
localnet.sh
so that it will work with containerized environments as well