Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

ff init command does not work

Abierto
  • ¿Algo no está bien?
#301 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
38/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
docker-compose, go
Área
cli, devops

Línea de trabajo

Reproduce ff init ethereum con Docker Compose v2.14.2 instalado y sigue la detección de la versión de Docker Compose utilizada por la CLI. El issue estará terminado cuando se reconozca la versión instalada de Compose y la inicialización continúe más allá de la comprobación de versión.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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?

Lenguaje dominante
Go
Estrellas
66
Forks
64
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de hyperledger-firefly/cli

Todos los issues de hyperledger-firefly/cli

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.