Awesome! Make sure you use Docker named volumes for the data. It is a 
current limitation that I hope to correct soon.

On Thursday, March 8, 2018 at 2:45:59 PM UTC-4, Raul wrote:
>
> I was able to get it working by building it by myself with docker-compose.
> Nice jobs guys :)
>
>
> Am Donnerstag, 8. März 2018 19:09:57 UTC+1 schrieb Raul:
>>
>> I just tried to start run that image. However, it stucks in a rebooting 
>> loop.
>> Do you know what I can do?
>> Is the image working?
>>
>> Thanks
>>
>> Am Donnerstag, 1. März 2018 09:45:37 UTC+1 schrieb [email protected]:
>>>
>>> The Docker image is available from the Docker Hub at: 
>>> https://hub.docker.com/r/mayanedmsng/mayanedmsng/
>>>
>>> Every procedure is the same as with the upstream version with the only 
>>> change that the repository reference must be mayanedmsng/mayanedmsng 
>>> instead of mayanedms/mayanedms.
>>>
>>> Once change this image has is that is includes a fourth worker to handle 
>>> the OCR and parsing queues. This worker is run with the lowest possible 
>>> process priority (19). Therefore OCR results might take longer than with 
>>> the upstream image. The advantage is that the OCR will not slowdown the 
>>> execution of the rest of the program. The total image layers were reduced 
>>> from 54 to 44. Total image size remained the same 1.32GB and 490.8MB 
>>> compressed (the actual download).
>>>
>>> Other changes according to Docker's best practices were made (pinning 
>>> installs to a specific version, not running dist-upgrade, etc).
>>>
>>> The repository for this image is here: 
>>> https://gitlab.com/e.riggs/mayan-edms-docker/commits/master
>>>
>>> I will continue working on getting the size of the image down. I'll also 
>>> keep trying using other base images instead of Ubuntu and or update to a 
>>> more recent version of Ubuntu, as time allows.
>>>
>>>
>>>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to