Odin container immediately exits 0

Question

Odin container immediately exits 0

Jafner opened this issue 9 months ago · comments

Following the steps described in the setup docs, the memgraph and bor containers appear to launch and run fine, but the odin container exits with the following log text:

odin      | Lifecycle scripts included in magic-graph@1.0.0:
odin      |   version
odin      |     node version-bump.mjs && git add manifest.json versions.json
odin      |
odin      | available via `npm run-script`:
odin      |
odin      |   dev
odin      |     node esbuild.config.mjs
odin      |   build
odin      |     tsc -noEmit -skipLibCheck && node esbuild.config.mjs production
odin      |
odin      |
odin exited with code 0

No changes were made to the docker-compose file.

This is running Docker Desktop on Windows 11.

howie.serious · Answer 1 · Tue Sep 26 2023 14:01:29 GMT+0800 (China Standard Time)

same problem here.

matayaaa · Answer 2 · Wed Sep 27 2023 14:35:20 GMT+0800 (China Standard Time)

Same. I've been playing around for hours now and can't get ODIN working.

Also seeing this in terminal.. "WARN[0000] The "MOCK" variable is not set. Defaulting to a blank string. "

Can see plugin successfully installed but it will not load

cir · Answer 3 · Mon Oct 02 2023 19:44:05 GMT+0800 (China Standard Time)

same here!
the plugin is visible within obsidian, but can't be enabled (failed to load plugin ODIN).

Lewis Crawford · Answer 4 · Sun Oct 08 2023 17:33:11 GMT+0800 (China Standard Time)

Same here - but on OSX other two containers running but Odin exited.

docker logs 937222727a48
Lifecycle scripts included in magic-graph@1.0.0:
version
node version-bump.mjs && git add manifest.json versions.json

available via npm run-script:
dev
node esbuild.config.mjs
build
tsc -noEmit -skipLibCheck && node esbuild.config.mjs production

Lifecycle scripts included in magic-graph@1.0.0:
version
node version-bump.mjs && git add manifest.json versions.json

available via npm run-script:
dev
node esbuild.config.mjs
build
tsc -noEmit -skipLibCheck && node esbuild.config.mjs production

Daniel Backus · Answer 5 · Wed Nov 08 2023 23:46:01 GMT+0800 (China Standard Time)

FYI I experienced this issue but was able to resolve it.

It appears the Odin container is intended to exit as it simply uses esbuild to compile the plugin which Obsidian consumes. However, it doesn't seem to actually work as intended in Docker. I just manually called the build script (i.e. npm run build), and then I was able to enable the plugin in Obsidian.

After this, calls to OpenAI API still were failing until I added LLM_MODEL_NAME=chatgpt4 environment variable to the bor container in the docker-compose.yml.

After this, calls to OpenAI API began succeeding but I still can't see any output in Obsidian. If/when I have time, next step is to dig further into the backend code at https://github.com/memgraph/bor to see what's happening.

Oleksandr Ichenskyi · Answer 6 · Wed Mar 06 2024 15:29:53 GMT+0800 (China Standard Time)

Hello everyone and thank you for your interest in Odin! I'm happy to announce that I've managed to fix this issue. Despite Odin still being considerably unstable, Docker and Docker Compose should now work as intended. I'm closing this issue as completed, but please feel free to open new issues and contribute to Odin and Bor. Your contributions can help make Odin better. Special thanks to @danielbackus - looking forward to seeing your contributions :) Any input is highly appreciated!