hyperledger-firefly / hyperledger-firefly/cli
Sandbox does not work when using "-e1"
Open
good first issue
- Dominant language
- Go
- Stars
- 66
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Description
If you start a stack for development with "-e1", the sandbox is broken. It still tries to connect to a container named (for instance) `firefly_core_0`, which does not exist when using the "external" option.
Contributor guide
Assessment
This issue has not been assessed yet.