Closed soulmerge closed 1 year ago
hmm this might just be bad instructions? the database is empty at this point and i cant see what is supposed to create anything in there.
edit: there's multiple issues here.
mariadb:10
instead of 11this commit removes gromox-dbop
https://github.com/grommunio/gromox-container/commit/af0e6969f52b6cac570c5091fe02edce76cf9b01
which according to this manual is required to setup the database
https://docs.grommunio.com/admin/manual_install.html#gromox-user-database
however, i cant get to work either. not sure if that's maybe the reason it was removed
Hi @aep, thank you for using our containers. I am unable to replicate the issue you have with decimal.InvalidOperation
. That might be specific to your platform or installation. Please can you give me further details about your platform?
hmm this might just be bad instructions? the database is empty at this point and i cant see what is supposed to create anything in there.
edit: there's multiple issues here.
* the decimal.InvalidOperation thing goes away by using `mariadb:10` instead of 11 * the startup sequence is fragile. apparantly the python thing doesnt retry later if the mysql db happens to be not ready * the docs are missing a step somewhere. the database is empty so you cant actually login
About the startup sequence, if you check the docker-compose example, the containers depend on the DB starting up before they start. That's a hard requirement. So, please ensure that you have the DB ready before the gromox-core
container and grommunio-admin
container starts up.
About the database, the gromox-core
container populates the DB. So you need that container to be up and running before you can do anything useful.
The commit you refer to removes the db population from the grommunio-admin
container.
Do you have the gromox-core
container up and running?
@aep, as a side note, I would suggest that you still use the this container for now. This has all the services in one container.
We are still handling some volume and shared storage issues on the v0.3 where we split out the services
I am unable to replicate the issue you have with decimal.InvalidOperation
docker pull mariadb
might help to reproduce. the compose file doesnt specify a version, so its whatever was last pulled on your machine, which might be 10. 10 works fine. 11 does not
the containers depend on the DB starting up before they start.
service_started doesnt indicate if mariadb is ready or not. it just means docker has started the service. by random chance this somtimes works out. if the software is unable to retry connection, what we usually do is either use service_healthy https://stackoverflow.com/a/41854997/1993710 or just or wrap the initscript in a port wait https://unix.stackexchange.com/a/5279/566568
About the database, the gromox-core container populates the DB.
it didnt. could you tell me where it does that so i can try to figure out why that doesnt work?
thanks
docker pull mariadb
might help to reproduce. the compose file doesnt specify a version, so its whatever was last pulled on your machine, which might be 10. 10 works fine. 11 does not
Great catch, thank you. I will check this out.
service_started doesnt indicate if mariadb is ready or not. it just means docker has started the service. by random chance this somtimes works out. if the software is unable to retry connection, what we usually do is either use service_healthy https://stackoverflow.com/a/41854997/1993710 or just or wrap the initscript in a port wait https://unix.stackexchange.com/a/5279/566568
Thank you for the information here and we are aware of it. The docker compose setup is an example recipe. We noted that you may need to make changes to suit your environment / use case.
it didnt. could you tell me where it does that so i can try to figure out why that doesnt work?
The setup for the db is here. I found the issue that might have caused it. Some changes in v0.2 affected the dependencies. I will fix it today
A couple of new changes will hit the repo later today. Please use the v0.1 for now as I suggested. The new version will be out tomorrow or over the weekend
Edit: @aep There's an update now. It will reach this repo tomorrow but the images on dockerhub are already updated. You should not have the previous problems with the split containers. I am still testing so please feel free to let me know whatever issues you notice.
The issues pointed out here have been fixed. I will close the issue now. Please feel free to open another issue if anything surfaces again
Just wanted to give this suite a try, but when following the installation guide in the examples folder, I em encountering the folloing error after running
docker-compose up
:The application seems to start, but all requests cause the following error in the logs, of course:
I think the behavior was slightly different, when I had started everything for the first time. I think the application was starting up fine, but I was getting a slightly different error about decimal conversation. Not sure about that, though, as I don't have the logs any more.
Please let me know if I can provide further information :-)