Errors when starting containers about docker-otrs

[juanluisbaptiste]

Did you test it with the original yml file ? I haven't tested it without volumes because it doesn't make sense for a production environment.

[zoell]

Yeah its the same error with the original file.

Could you please check if you can run this with docker-compose up?

[juanluisbaptiste]

When using the defaullt yml file, did you check the file system permissions as described on the README ?

[zoell]

Yes

[juanluisbaptiste]

I just tested the default yml file and it works fine. Most of the problems come from the permissions of the directories that hold the container volumes as explained on the README file.

[zoell]

That is intereting.

So to just start at the beggining, with zero (or almost zero) configuration what I have to do is:

1: clone the repo
2: add the files:
for otrs: otrs-setup.env
for postfix: credentials-smtp.env
3: change to OTRS_INSTALL: "yes"

and do docker-compose up right? I want to replicate exactly what you have done to try it out.
Btw do you have an example for those two env files?

[juanluisbaptiste]

You don't list to check/fix directory permissions, please check the README and fix permissions before starting the service.

[zoell]

I did that already as I mentioned.
Please give me an example for the env files.

[juanluisbaptiste]

The error you posted has to do with filesystem permissions, it has nothing to do with env files. You can remove them and put all the env variables on the yml file and the error should be the same. Test with the docker-compose-prod.yml file (which doesn't use env_file), the other one I use it to build the images, and use the -prod one as a base for my production installations (but using env_file).

[juanluisbaptiste]

Also don't use OTRS_INSTALL=yes (the default is no), the default install is ready to be configured, you don't need to do the installation, that parameter is more for tests and haven't tested it in a long time.

[zoell]

Thanks, the issue was with the OTRS_INSTALL=yes.