New instance not working

[fmnamado]

Hello,

I could user some help here.

I just installed a new piler instance on another VM.
Followed the procedure on the page.

Using the Piler on the command line
For use on the command line, we first log into the container.
docker exec -it piler /bin/bash
Next we switch to the user "piler"
su piler
To get write permissions, we switch to the /var/tmp folder
cd /var/tmp

I get this criptic message

$ pilerimport -m emails.mbox
error parsing the configfile: /etc/piler/piler.conf

IK also tried root inside the container, before the su piler, as it seems the piler user does not have read rights on piler.conf

What can be the problem? It is a fresh install on a just git cloned repo.

Thank you, I am going nuts.

[fmnamado]

OK I got to the issue, it is a permissions issue....

For some reason my sometime-ago installation has piler as the owner and group owner of /etc/piler/piler.conf (inside the /docker exec -it piler /bin/bash command).

This new installation DOES NOT.
The owner and group owner is root

that is why it was failing parsing it, because it could not read it.
That is why the cat would not work as piler user logged in.

Three questions arise:
-Was I to blame for this? I think not, I just ran the install script.
-Switching it manually to chown piler:piler piler.conf solved this, now the import works. Will I have undesired consequences on this?
-If this is a bug, can someone solve this for others?

Thank you!