-
Notifications
You must be signed in to change notification settings - Fork 4
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 up fails #6
Comments
How about now? |
pull and rerun Can be an issue on mac os m1? |
Same result after pull? Weird.
Can't exclude the possibility, but it doesn't sound very likely. Fundamentally, it's issue with us trying to cover like 3 different workflows with the same Docker Compose config, and new users finally beginning to discover some of the inevitable blind spots 😁 It's failing to find something around the build of the WASM component that is part of @fadroma/namada. But, of course, it's not reporting what exact path is not being found. (Otherwise it would've been too damn easy 🤣) Without more context I can't be sure what exactly is going wrong, so you might need to mess around with that step of the Dockerfile some more until it spits out some more info |
@RuslanGlaznyov There are now two separate Docker Compose setups.
See if this fixes your issue? |
@RuslanGlaznyov can you try removing cached docker images, volumes and containers associated with the undexer. Then pull from main and try starting with |
Docker compose up doesn't work from main branch
The text was updated successfully, but these errors were encountered: