Ok, i reply to myself as i could resolve the problem by changing the alpine Linux image to Debian light.
After debugging, the problem seems to be the compilation option used for alpine packets, which is not fully compatible when running on NAS Intel cpu.
The problem disappeared with Debian light, which should be less "aggressive" for optimization. I think the core is generated during imagemagick lib call (png, jpeg,pdf, ...).
Cheers
Laurent Jean-Rigaud wrote: |
Hi,
I currently testing last ELOG version from git in a docker with LDAP activated (https://hub.docker.com/r/usinagaz/elog-ldap). The goal is to use it on Synology NAS server, associated with local LDAP server.
The reverse proxy is done by embedded DSM nginx, according to FDQN associated to ELOG service (elog.corp.com). In Docker, URL is set to elog.corp.com.
All is good, but when I post any enclosure in any elog post, the elogd exits and docker is automatically restarted. The browser shows an error 405 generated by nginx server.
Do you have any idea of the cause of this problem ?
Thanks for help.
Laurent
|
|