Skip to content
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

Docker compose problems on zksync-cli dev start #151

Open
alexhooketh opened this issue Jul 9, 2024 · 1 comment
Open

Docker compose problems on zksync-cli dev start #151

alexhooketh opened this issue Jul 9, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@alexhooketh
Copy link

🐛 Bug Report for zkSync CLI

📝 Description

I'm not at all sure if it's actually a bug. I'm probably doing something wrong but still

I'm getting this error when trying to init a project:

jordan@Air-Alex contracts % zksync-cli dev start

? Node to use In memory node
? Additional modules to use Block Explorer
You can change the config later with `npx zksync-cli dev config`

ⓘ There was an error while starting the testing environment:
ⓘ Command exited with code 16: unknown docker command: "compose Support/fnm/node-versions/v18.19.0/installation/lib/node_modules/zksync-cli/node_modules/zkcli-in-memory-node/docker-compose.yml"

file:///Users/jordan/Library/Application%20Support/fnm/node-versions/v18.19.0/installation/lib/node_modules/zksync-cli/bin/utils/helpers.js:52
                reject(new Error(`Command exited with code ${code}: ${errorOutput}`));
                       ^

Error: Command exited with code 16: unknown docker command: "compose Support/fnm/node-versions/v18.19.0/installation/lib/node_modules/zksync-cli/node_modules/zkcli-in-memory-node/docker-compose.yml"

    at ChildProcess.<anonymous> (file:///Users/jordan/Library/Application%20Support/fnm/node-versions/v18.19.0/installation/lib/node_modules/zksync-cli/bin/utils/helpers.js:52:24)
    at ChildProcess.emit (node:events:517:28)
    at maybeClose (node:internal/child_process:1098:16)
    at Socket.<anonymous> (node:internal/child_process:450:11)
    at Socket.emit (node:events:517:28)
    at Pipe.<anonymous> (node:net:350:12) {
  level: 'error',
  [Symbol(level)]: 'error',
  [Symbol(message)]: '\x1B[91mⓘ Command exited with code 16: unknown docker command: "compose Support/fnm/node-versions/v18.19.0/installation/lib/node_modules/zksync-cli/node_modules/zkcli-in-memory-node/docker-compose.yml"\x1B[39m\n' +
    '\x1B[91m\x1B[39m'
}

Node.js v18.19.0

I'm running a Docker Desktop, but I have no idea how it works, so I might need to enable something in it. Node and zksync-cli were just installed using brew and npm i respectively

🔄 Reproduction Steps

  1. run docker desktop
  2. brew install node
  3. npm i -g zksync-cli
  4. zksync-cli dev start
  5. select all the stuff about the project
  6. boom

🤔 Expected Behavior

the project initializes

😯 Current Behavior

the project does not initialize

🖥️ Environment

  • Package version: 1.7.2 (zksync-cli --version)
  • Node version: v18.19.0
  • NPM/Yarn version: npm 10.2.3
  • Operating System & Version: macOS 14.5 (23F79)
  • Other relevant environment details: Docker Desktop: Version 4.31.0 (153195) Engine: 26.1.4 Compose: v2.27.1-desktop.1 Credential Helper: v0.8.2 Kubernetes: v1.29.2

📋 Additional Context

ZKsync Docs say nothing about Docker at all but I just assumed it's necessary because of docker compose error.
image
image

@alexhooketh alexhooketh added the bug Something isn't working label Jul 9, 2024
@alexhooketh
Copy link
Author

now that i look at it the problem might be in the space in the path

Command exited with code 16: unknown docker command: "compose Support/fnm/node-versions/v18.19.0/installation/lib/node_modules/zksync-cli/node_modules/zkcli-in-memory-node/docker-compose.yml"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant