-
Notifications
You must be signed in to change notification settings - Fork 5
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
Deploy mpc development network to the ground #3
Labels
Comments
sbellem
changed the title
Deploy mpc network to the ground
Deploy mpc development network to the ground
Feb 1, 2021
See if secrets can be mounted from local file: https://docs.docker.com/cloud/ecs-compose-examples/#secrets |
Happening when only dev geth node & mpc nodes are deployed on aws, without client requests/actions. (No contract deployed, not pool initialized, no deposits, no trades.) d809820ae0fc4a77a079c10652997c72 | Inputmaks shares used: <nil>
d809820ae0fc4a77a079c10652997c72 | panic: runtime error: invalid memory address or nil pointer dereference
d809820ae0fc4a77a079c10652997c72 | [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x978884]
d809820ae0fc4a77a079c10652997c72 | goroutine 7 [running]:
d809820ae0fc4a77a079c10652997c72 | math/big.(*Int).Int64(...)
d809820ae0fc4a77a079c10652997c72 | /usr/local/go/src/math/big/int.go:374
d809820ae0fc4a77a079c10652997c72 | github.com/initc3/HoneyBadgerSwap/src/go/utils.GetInputmaskCnt(0xc0000ac798, 0x0)
d809820ae0fc4a77a079c10652997c72 | /go/src/github.com/initc3/HoneyBadgerSwap/src/go/utils/utils_hbswap.go:327 +0x144
d809820ae0fc4a77a079c10652997c72 | main.genInputmask(0x7ffed7e73b65, 0x8)
d809820ae0fc4a77a079c10652997c72 | /go/src/github.com/initc3/HoneyBadgerSwap/src/go/server/server.go:58 +0x45
d809820ae0fc4a77a079c10652997c72 | created by main.main
d809820ae0fc4a77a079c10652997c72 | /go/src/github.com/initc3/HoneyBadgerSwap/src/go/server/server.go:306 +0x29c
d809820ae0fc4a77a079c10652997c72 | exit status 2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Not essential, but preferable whenever possible
plyvel
instead ofleveldb
UPDATE: We are using the docker compose cli ECS integration .
Since we already have docker containers + docker-compose to manage these containers, see what provider may be most convenient & simple.
Follow https://docs.docker.com/cloud/ecs-integration/#install-the-docker-compose-cli-on-linux
Resources
First stop for tooling: Amazon ECS developer tools overview
There seems to be 3 main approaches:
To re-use an existing compose file, the
compose-cli
may be best suited. See: https://aws.amazon.com/blogs/containers/deploy-applications-on-amazon-ecs-using-docker-compose/.docker compose-cli
Secrets + Docker
Volumes
Other tools
copilot
ecs-cli
Challenges
Some challenges relating to deployments.
The text was updated successfully, but these errors were encountered: