Closed RuslanGlaznyov closed 2 weeks ago
How about now?
pull and rerun with docker compose up --build --force-recreate --no-deps
Can be an issue on mac os m1?
Same result after pull? Weird.
Can be an issue on mac os m1?
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 :grin:
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 :rofl:) 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.
Staging: docker-compose.yml
(the one currently referenced in the Justfile
). This does not mount the source. So it should not fail to find the WASM file from @fadroma/namada (which is built by the Dockerfile, but the host volumes were masking it.)
Development: docker-compose.dev.yml
. This is how the Compose used to be set up before the fix. It mounts the source code from the repo into the containers (volumes
clause in service config), so that one may edit the Undexer code and restart to see changes. However, to run it you must manually pre-build the WASM using pnpm build:wasm:dev
(or copy it from a staging-mode container using docker cp
, etc, I guess?)
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
again?
Closing for inactivity; @RuslanGlaznyov note that the upcoming 0.4.0 release will not be possible to run without Docker (see https://github.com/hackbg/undexer/issues/11#issuecomment-2455421210); thus, the issue which you encounter continues to be important. We'll be happy to have your feedback once 0.4.0 is out.
Docker compose up doesn't work from main branch