From 4b2a670e137f419b95f531811613fdcdb4d1d07a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=B6rn=20Friedrich=20Dreyer?= Date: Mon, 17 Aug 2020 15:06:18 +0200 Subject: [PATCH] add eos truobleshooting docs MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Jörn Friedrich Dreyer --- docs/eos.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/eos.md b/docs/eos.md index 3a735c80b6..691f9a3087 100644 --- a/docs/eos.md +++ b/docs/eos.md @@ -172,3 +172,15 @@ EOS Console [root://localhost] |/> But this is a different adventure. See the links at the top of this page for other sources of information on eos. + +## Troubleshooting + +Q: When running `docker-compose up -d` ocis exits right away. +A: You can check the error code using `docker-compose ps` and investigate further by running only ocis again using `docker-compose up ocis` (without `-d` so you can see whet is going on in the foreground). +One reason might be that the binary was already built and but does not match the container env. Try running `make clean` before running `docker-compose up ocis` so it gets built inside the container. + +Q: How do I update a service in the ocis container? +A: 1. `docker-compose exec ocis make clean build` to update the binary + 2. `docker-compose exec ocis ./bin/ocis kill ` to kill the service + 3. `docker-compose exec ocis ./bin/ocis run ` to start the service. Do not forget to set any env vars, eg. + `docker-compose exec -e REVA_STORAGE_EOS_LAYOUT="{{substr 0 1 .Id.OpaqueId}}/{{.Id.OpaqueId}}" -e REVA_STORAGE_HOME_DRIVER=eoshome ocis ./bin/ocis run reva-storage-home` \ No newline at end of file