ff init command does not work
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Reproduce ff init ethereum with Docker Compose v2.14.2 installed and trace the Docker Compose version detection used by the CLI. The issue is done when the installed Compose version is recognized and initialization proceeds past the version check.
Written by the indexing model from the issue text.
Description
Hello,
I installed Firefly binary and cannot initiate a stack.
After inserting the stack name and the number of nodes on it via prompt, the CLI returns: "Error: no version for docker-compose has been detected". although I hvve Docker Compose installed on my local machine.
Here follows a printscreen of my terminal.
firefly$ docker-compose --version
Docker Compose version v2.14.2
firefly$ ff init ethereum
initializing new FireFly stack...
stack name: dev
You selected dev
number of members: 3
Error: no version for docker-compose has been detected
Usage:
ff init ethereum [stack_name] [member_count] [flags]
Flags:
--block-period int Block period in seconds. Default is variable based on selected blockchain provider. (default -1)
-c, --blockchain-connector string Blockchain connector to use. Options are: [evmconnect ethconnect] (default "evmconnect")
-n, --blockchain-node string Blockchain node type to use. Options are: [geth besu remote-rpc] (default "geth")
--chain-id int The chain ID - also used as the network ID (default 2021)
--contract-address string Do not automatically deploy a contract, instead use a pre-configured address
-h, --help help for ethereum
--remote-node-url string For cases where the node is pre-existing and running remotely
Global Flags:
--ansi string control when to print ANSI control characters ("never"|"always"|"auto") (default "auto")
--channel string Select the FireFly release channel to use. Options are: [stable head alpha beta rc] (default "stable")
--connector-config string The path to a yaml file containing extra config for the blockchain connector
--core-config string The path to a yaml file containing extra config for FireFly Core
-d, --database string Database type to use. Options are: [sqlite3 postgres] (default "sqlite3")
-e, --external int Manage a number of FireFly core processes outside of the docker-compose stack - useful for development and debugging
-p, --firefly-base-port int Mapped port base of FireFly core API (1 added for each member) (default 5000)
--ipfs-mode string Set the mode in which IFPS operates. Options are: [private public] (default "private")
-m, --manifest string Path to a manifest.json file containing the versions of each FireFly microservice to use. Overrides the --release flag.
--multiparty Enable or disable multiparty mode (default true)
--node-name stringArray Node name
--org-name stringArray Organization name
--prometheus-enabled Enables Prometheus metrics exposition and aggregation to a shared Prometheus server
--prometheus-port int Port for the shared Prometheus server (default 9090)
--prompt-names Prompt for org and node names instead of using the defaults
-r, --release string Select the FireFly release version to use. Options are: [stable head alpha beta rc] (default "latest")
--remote-node-deploy Enable or disable deployment of FireFly contracts on remote nodes
--request-timeout int Custom request timeout (in seconds) - useful for registration to public chains
--sandbox-enabled Enables the FireFly Sandbox to be started with your FireFly stack (default true)
-s, --services-base-port int Mapped port base of services (100 added for each member) (default 5100)
-t, --token-providers stringArray Token providers to use. Options are: [none erc1155 erc20_erc721] (default [erc20_erc721])
-v, --verbose verbose log output
Error: no version for docker-compose has been detected
firefly$
Does anyone know how to fix that issue? How to make Firefly recognize Docker Compose version?
- Dominant language
- Go
- Stars
- 66
- Forks
- 64
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from hyperledger-firefly/cli
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
hyperledger-firefly/cli#357 ·
-
bug good first issue
Difficulty 3/5 1-2 days Newbie friendliness 45/100
hyperledger-firefly/cli#343 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
hyperledger-firefly/cli#339 · 7 comments ·
-
bug Windows WSL
Difficulty 3/5 1-2 days Newbie friendliness 25/100
hyperledger-firefly/cli#335 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
hyperledger-firefly/cli#334 · 2 comments ·
All issues in hyperledger-firefly/cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
[Bug]: APIGW request ID headers are inconsistent between server and clientPossibly taken @zouxingyuks claimed this today. Openproduct/backlog
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
TencentBlueKing/bk-nodemgr#3782 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 91/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
praetorianer777/Dynamo#53 ·
Maintainers usually reply within 1 day
-
internal test setup
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SAP/terraform-provider-scc#430 ·