Unable to mount /etc/apcupsd/ as a volume about apcupsd HOT 4 CLOSED

Hi, thanks for trying out my container.

Removing the ‘confit’ volume will mean that you don’t get persistent configuration. What I’d recommend here is to run it once without the volume, configure it and then copy the resultant config file out from the running container. Then put that config file in the folder on the host and re-add the volume list e to your compose. This should mean that you get your customised config file each time the container starts.

from apcupsd.

Yes, I know that without mounting the volume the configuration won't survive a container recreation, I've created the issue because on other containers I am able to mount the directory on the host from the first start and I am able to manage all the configurations from there without getting errors. I will try your suggestion and let you know.
Nice work with this container btw, I was exactly looking at something like this

from apcupsd.

Hi, just wanted to check if you were able to resolve the problem ?

from apcupsd.

Closing issue as there have been no updated in a month.

from apcupsd.