Issue using docker-compose file about patzilla

[amotl]

Hi there,

thanks for writing in.

Intro

thanks for putting together such a nice application!

Thanks for the kind words, we are always happy to welcome new people interested in this and we are just getting started. The project will be happy to receive stars on GitHub ;].

I understand that the docker-compose means of installation is probably not supported yet, just wanted to point out the issue.

@aghster put that together the other day. To be honest i haven't actually used it yet as i usually run PatZilla in development mode natively on my workstation. Nevertheless, i was very happy about his contribution and will be glad if we can resolve this issue together.

Also had to add a couple of things to the docker files to get things to work, happy to make a pull request when desired.

Looking forward! Did you even manage to get Open Office inside? Through unoconv, it is used to do some rendering for specific export artefacts.

The issue itself

It looks like Pyramid is pretty clear on what happened: TemplateLookupException: Can not locate template for uri probably means what it says: The application can not access the template in question. So, it is probably some packaging / search path issue.

Maybe @aghster knows something about this error? If not, i will be happy to investigate further.

With kind regards,
Andreas.

[aghster]

Hi, I just reviewed the docker files and made some modifications, cf. pull request #6.

I have identified two possible causes for an error. First, a dependency was missing. Second, for patzilla to run properly when executing "docker-compose up -d", a configuration file named patzilla.ini had to be present in the folder, where docker-compose.yml is run from.

The dependency is now fixed and a default patzilla.ini is now provided. So I would expect that executing "docker-compose up -d" within the docker/ folder should start up a patzilla container out-of-the-box. However, one should still customize patzilla.ini (in particular, at least to include custom api keys) before running the container.

I do not know whether the errors @blubbi321 encountered are caused by any of these two issues that I have adressed by my amendments, since the error message provided by @blubbi321 prima facie does not seem related to docker. Therefore, I also do not know whether these errors are now fixed by the amendments. But when I now clone the repository, change into the docker/ folder and execute "docker-compose up -d" I can access a running patzilla instance through "127.0.0.1:9999/navigator" in my browser.

[blubbi321]

@aghster thanks for your quick reply. I had done a bunch of your modifications already, but apparently not enough.

Just tried to clone your repo's "docker-mods" branch and if I run the containers as suggested I get a

404 Not Found
The resource could not be found.

/navigator

from http://127.0.0.1:9999/navigator

[aghster]

This could be due to a missing trailing slash. Please try:

http://127.0.0.1:9999/navigator/

[blubbi321]

http://127.0.0.1:9999/navigator/

omg, then I probably had the thing running a couple of times already :D

Thanks again for your quick reply (and of course your pull request)!

Regarding the OO installation that @amotl mentioned above: I didnt try that as I was unaware it was required. I also dont see it in your dockerfiles, so Im wondering whether its required at all?

[aghster]

Sorry for the missing slash.

I do not think that OO is included, when patzilla is installed from pypi using pip, as is the case in the docker image. Also, I do not think that OO is actually required, since according to @amotl it just serves to do "some rendering for specific export artefacts". To my understanding @amotl simply suggested (or hoped for) that unoconv be included into the image to extend patzilla's functionality. Unfortunately, there seems to be no pre-built unoconv package for alpine (cf. https://pkgs.alpinelinux.org/packages?name=unoconv&branch=edge). Therefore, one would have to install unoconv and include the required LibreOffice or OpenOffice libraries manually.

[amotl]

When trying to run the installation on my machine, the process of docker-compose up will croak when trying to install the pillow package as a dependency of the patzilla package:

The headers or library files could not be found for jpeg,
a required dependency when compiling Pillow from source.

[aghster]

That was with the old Dockerfile. With the new one this error should be fixed, since jpeg-dev is now included in the packages that are installed in the image. Is it not? Can you check that your Dockerfile includes jpeg-dev?

[amotl]

Ah, just have been reading the comments as well as #6:

I fixed a missing dependency (jpeg-dev, apparently required by pillow) and added some optional libraries (freetype-dev, lcms2-dev, tiff-dev) that I considered possibly useful.

Thank you so much, guys!

[amotl]

@aghster said:

This could be due to a missing trailing slash. Please try:

http://127.0.0.1:9999/navigator/

@blubbi321 said:

omg, then I probably had the thing running a couple of times already :D

I am so sorry about this little detail which I believe is frustrating when getting started. Note to self: Will have to address it more appropriately, at least in the documentation.

Glad you have been able to sort this out. At least now it's documented here, which is not a bad place either.