Having trouble running pacoloco via Docker

[987computer]

When I try to start the Docker container after building it with the provided instructions (as well as putting the config file listed below), this is what it returns:

pacoloco.go:102: Reading config file from /etc/pacoloco.yaml
pacoloco.go:105: read /etc/pacoloco.yaml: is a directory

[anatol]

cc @ilya-zlobintsev

[anatol]

/etc/pacoloco.yams is a config file. It must not be a directory. Check your filesystem content.

[ilya-zlobintsev]

Are you sure that you've created the config file? By default if the host path specified in a volume doesn't exist, docker will create it as a directory.

[987computer]

Yeah. In fact, I already created it beforehand after getting that error. Trying the same steps with that said config file in the "etc" directory returns the same result.

[cocoonkid]

@987computer Did you ever solve this? Docker works perfectly for me here.

[Focshole]

When I try to start the Docker container after building it with the provided instructions (as well as putting the config file listed below), this is what it returns:

pacoloco.go:102: Reading config file from /etc/pacoloco.yaml pacoloco.go:105: read /etc/pacoloco.yaml: is a directory

Try logging into the docker container , then check what is going on in /etc/pacoloco.yaml

[HarHarLinks]

docker works perfectly here.

@987computer: you appear to not have created the yaml file before starting the container and/or in the wrong place. Docker will create an empty directory of that name in those cases, which leads to this error.

1. You need to stop and any existing container.
2. Create the pacoloco.yaml file at a reasonable place on your host system. I use /opt/pacoloco/pacoloco.yaml (next to /opt/pacoloco/cache/).
3. Then look at where the example command or compose file says /path/to/config/pacoloco.yaml:/etc/pacoloco.yaml.
4. Set the left part of the argument to the path on your host. In my example that means you get /opt/pacoloco/pacoloco.yaml:/etc/pacoloco.yaml.
5. Run.

[Focshole]

Shall we close this issue?

[fhteagle]

--- Disregard, docker-compose up -d pacoloco fixed my issue ---