[GH-ISSUE #128 ] Build in Postgres removed in 5.2? #74

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Oct 2, 2018):

@poVoq no, we do not remove postgres, could you show full docker run command to investigate your problem

@ShockwaveNN commented on GitHub (Oct 2, 2018): @poVoq no, we do not remove postgres, could you show full `docker run` command to investigate your problem

kerem commented

Author

Owner

@poVoq commented on GitHub (Oct 2, 2018):

I am running it through Portainer, so I don't really know the docker run command.
I just now tried going back to 5.1.5.59 and it works, but now (was not the case before) seems to restart itself every 30 seconds or so.

@poVoq commented on GitHub (Oct 2, 2018): I am running it through Portainer, so I don't really know the docker `run command`. I just now tried going back to 5.1.5.59 and it works, but now (was not the case before) seems to restart itself every 30 seconds or so.

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Oct 2, 2018):

@poVoq We do not perform any major changes in postgres methods so you should investigate your porter installation.
Main change some Docker code to work without interactive flag
https://github.com/ONLYOFFICE/Docker-DocumentServer/pull/99
but I'm not sure how it can be related with Portainer

@ShockwaveNN commented on GitHub (Oct 2, 2018): @poVoq We do not perform any major changes in postgres methods so you should investigate your porter installation. Main change some Docker code to work without interactive flag https://github.com/ONLYOFFICE/Docker-DocumentServer/pull/99 but I'm not sure how it can be related with Portainer

kerem commented

Author

Owner

@poVoq commented on GitHub (Oct 2, 2018):

Ok seems like after removing all the old volumes and starting from scratch it is working, I still run it with interactive flag though. I guess something goes wrong with the update process?

@poVoq commented on GitHub (Oct 2, 2018): Ok seems like after removing all the old volumes and starting from scratch it is working, I still run it with interactive flag though. I guess something goes wrong with the update process?

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Oct 2, 2018):

@poVoq can you describe which volumes you're left while updating from 5.1 to 5.2, I try to check it

@ShockwaveNN commented on GitHub (Oct 2, 2018): @poVoq can you describe which volumes you're left while updating from 5.1 to 5.2, I try to check it

kerem commented

Author

Owner

@poVoq commented on GitHub (Oct 2, 2018):

I have linked as named volumes:
/var/lib/onlyoffice
/var/lib/postgresql
/var/log/onlyoffice
/var/www/onlyoffice/Data
/etc/onlyoffice
/usr/share/fonts/truetype/custom

Initially I just tried removing the /var/lib/postgresql one, but that didn't make a difference. Afterwards I replaced all and it worked.

Note however that I had this Docker image working for a while now with various 5.1 versions that were released since 1 year I guess, and I always upgraded the image without touching the volumes without issues.

@poVoq commented on GitHub (Oct 2, 2018): I have linked as named volumes: /var/lib/onlyoffice /var/lib/postgresql /var/log/onlyoffice /var/www/onlyoffice/Data /etc/onlyoffice /usr/share/fonts/truetype/custom Initially I just tried removing the /var/lib/postgresql one, but that didn't make a difference. Afterwards I replaced all and it worked. Note however that I had this Docker image working for a while now with various 5.1 versions that were released since 1 year I guess, and I always upgraded the image without touching the volumes without issues.

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Oct 2, 2018):

@poVoq oh, I think /etc/onlyoffice is the problem, we go a troubles with updating with config between version (previously you update withing 5.1 and bugfixes, it's fine, but we got troubles in 5.1 -> 5.2)
I take a look at this

@ShockwaveNN commented on GitHub (Oct 2, 2018): @poVoq oh, I think `/etc/onlyoffice` is the problem, we go a troubles with updating with config between version (previously you update withing 5.1 and bugfixes, it's fine, but we got troubles in 5.1 -> 5.2) I take a look at this

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Oct 2, 2018):

@poVoq ok. can I ask you there did you found information that /etc/onlyoffice should be mounted as volume?
I think me may have this in readme in past, but current https://github.com/ONLYOFFICE/Docker-DocumentServer/blob/master/README.md where I cannot find info about /etc/onlyoffice

@ShockwaveNN commented on GitHub (Oct 2, 2018): @poVoq ok. can I ask you there did you found information that `/etc/onlyoffice` should be mounted as volume? I think me may have this in readme in past, but current https://github.com/ONLYOFFICE/Docker-DocumentServer/blob/master/README.md where I cannot find info about `/etc/onlyoffice`

kerem commented

Author

Owner

@poVoq commented on GitHub (Oct 2, 2018):

I think it was automatically created as a non-named volume and as I absolutely hate those polluting my volume storage I replaced it :) So yeah, in that case maybe my own fault...

@poVoq commented on GitHub (Oct 2, 2018): I think it was automatically created as a non-named volume and as I absolutely hate those polluting my volume storage I replaced it :) So yeah, in that case maybe my own fault...

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Oct 2, 2018):

@poVoq we got same problem while testing openshift and fixed it, but do not released it though
github.com/ONLYOFFICE/Docker-DocumentServer@f03a23cccd
I think we can release release this fix in future

@ShockwaveNN commented on GitHub (Oct 2, 2018): @poVoq we got same problem while testing openshift and fixed it, but do not released it though https://github.com/ONLYOFFICE/Docker-DocumentServer/commit/f03a23cccd3d96036f66f9b3411720c9286d6a56 I think we can release release this fix in future

kerem commented

Author

Owner

@ShockwaveNN commented on GitHub (Oct 3, 2018):

@poVoq this fix will be released as 5.2.1
github.com/ONLYOFFICE/Docker-DocumentServer@23d320dc2a

I'm not sure this is exactly a fix of your problem, but since we got no more info - I close issue, feel free to comment if you find some more info how to reproduce your problem

@ShockwaveNN commented on GitHub (Oct 3, 2018): @poVoq this fix will be released as 5.2.1 https://github.com/ONLYOFFICE/Docker-DocumentServer/commit/23d320dc2a705dfb4450455a0c24f9f8841104b6 I'm not sure this is exactly a fix of your problem, but since we got no more info - I close issue, feel free to comment if you find some more info how to reproduce your problem

kerem commented

Author

Owner

@ghost commented on GitHub (Oct 10, 2018):

I seem to have the exact same problem after an update of the docker image from an older version to latest 5.2.2.2. After removing the unnamed volume for /etc/onlyoffice it works again.

@ghost commented on GitHub (Oct 10, 2018): I seem to have the exact same problem after an update of the docker image from an older version to latest 5.2.2.2. After removing the unnamed volume for `/etc/onlyoffice` it works again.

kerem commented

Author

Owner

@MnrGreg commented on GitHub (Jun 17, 2019):

@ShockwaveNN I see there have been some issues and fixes relating to minishift and OpenShift. Do you or anyone else have deployment manifests for Kubernetes?

@MnrGreg commented on GitHub (Jun 17, 2019): @ShockwaveNN I see there have been some issues and fixes relating to minishift and OpenShift. Do you or anyone else have deployment manifests for Kubernetes?

kerem commented