PillerImport : failing in docker

Issue #1307 wontfix
Jáder Marasca created an issue

I’m trying to run pilerimport on docker and getting an error about shared libraries not available

[root@piler importar]# /var/lib/docker/overlay2/ac65f9d76551ca8e42b4676d83500749790c4123bdca3d7d133b59a7f2526d70/merged/usr/bin/pilerimport -d Maildir/*
/var/lib/docker/overlay2/ac65f9d76551ca8e42b4676d83500749790c4123bdca3d7d133b59a7f2526d70/merged/usr/bin/pilerimport: error while loading shared libraries: libpiler.so.0.1.1: cannot open shared object file: No such file or directory

please note I’m using a whole path because I know NOTHING about docker.

I think it should adapt the path from environment, but I cannot find instructions about this in https://mailpiler.com/running-piler-enterprise-in-a-containerized-environment-with-docker-compose/

In other sites I found the solution WOULD BE compile static… so the libs are not necessary… but all about programming looks like KLINGON language…kkk

BTW: I'd love to understand how to use this LetsEncrypt part inside docker (where there are a NGINX/TIKA)

https://mailpiler.com/how-to-obtain-an-a-grade-lets-encrypt-certificate-with-traefik/

so I can have a valid SSL certificate on my docker environment… but maybe I should have it on host!

Comments (1)

  1. Janos SUTO repo owner

    Well, if you don't know anything about docker, then you should really not use piler in docker. The issue tracker is not the appropriate place for a docker crash course, please get familiar with containers and docker in general before attempting to run piler in docker. Btw. regarding the klingon stuff, it's definitely not the answer to compile piler statically.

  2. Log in to comment