-
Notifications
You must be signed in to change notification settings - Fork 182
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
initial docker-compose.yml for developers #349
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
After submitting the login form I see an error in the log.
And phoenix shows the login error screen. |
56522a1
to
5708ae8
Compare
@butonic with all the steps from above, I can login. But uploading a file (.jpg) results in:
in ocis logs and
in eos logs However, |
fixing /var/tmp/reva/shares.json in owncloud-archive/eos-stack#2 |
@felixboehm starting only ocis does not work without eos
|
Shouldn't we also fix it in the share manger? |
@C0rby what exactly? both create a file with The implementation can no doubt be improved, but AFAICT they already autocreate the file if it is missing. There might be problems when tryding to mount the file as a volume in a docker container though... would need a separate issue. |
I forgot to link it here. cs3org/reva#940 |
ci: no space left on device ... restarting |
I have added docs to the your PR for development with eos. I tested all the steps right now with eos-stack from PR owncloud-archive/eos-stack#4, which I will publish on docker hub as soon as merged. |
Hmm, still can reproduce the upload issue on eos, mentioned by @kulmann
maybe is the layout still not correct? Looks weird |
I can also reproduce @kulmann issue:
|
|
restarting the reva-users service allows it to pick up the changed ldap env. added to the docs. |
things we noticed while testing this:
|
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
use correct REVA_STORAGE_HOME_DATA_DRIVER env var for the reva-storage-home-data service
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
Signed-off-by: Jörn Friedrich Dreyer <jfd@butonic.de>
This PR adds a new docker-compose.yml file that allows developers to quickly spin up a development environment for ocis using both: the owncloud storage driver as well as the eos storage driver. For the latter it also contains the necessary eos containers
get started using the owncloud storage driver
docker-compose up -d ocis
docker-compose exec ocis bash -c "echo '{}' > /var/tmp/reva/shares.json"
docker-compose exec ocis make clean build
. this makes sure that all cgo bindings are there and the binary will work properly when resolving ldap usersdocker-compose exec ocis ./bin/ocis server
docker-compose exec ocis ./bin/ocis list
ocis will use the owncloud storage driver and store files in the container at
/var/tmp/reva/data/<username>/files
.start eos cluster:
docker-compose up quark-1 quark-2 quark-3 mgm-master mq-master fst
docker-compose exec mgm-master eos space set default on
otherwise you will encounter an out of space error (code 54) when trying to upload files.docker-compose exec ocis eos whoami
... should giveVirtual Identity: uid=0 (0,99,3) gid=0 (0,99,4) [authz:sss] sudo* host=ocis.testnet domain=testnet
switch to eos storage driver
docker-compose exec ocis ./bin/ocis kill reva-storage-home
docker-compose exec ocis ./bin/ocis kill reva-storage-home-data
docker-compose exec -e REVA_STORAGE_EOS_LAYOUT="{{substr 0 1 .Username}}/{{.Username}}" -e REVA_STORAGE_HOME_DRIVER=eoshome ocis ./bin/ocis run reva-storage-home
docker-compose exec -e REVA_STORAGE_EOS_LAYOUT="{{substr 0 1 .Username}}/{{.Username}}" -e REVA_STORAGE_HOME_DATA_DRIVER=eoshome ocis ./bin/ocis run reva-storage-home-data
docker-compose exec ocis ./bin/ocis kill reva-frontend
docker-compose exec -e DAV_FILES_NAMESPACE="/eos/" -d ocis ./bin/ocis reva-frontend
TODO