-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to mount /etc/apcupsd/ as a volume #1
Comments
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. |
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. |
Hi, just wanted to check if you were able to resolve the problem ? |
Closing issue as there have been no updated in a month. |
Hello, I wanted to mount /etc/apcupsd as a volume.
This is the docker-compose that I am using:
This is the error that I see if I run docker-compose logs -f
If I remove
- /apps/apcupsd/config:/etc/apcupsd:rw
from the compose file I have a working container without errors but I have to reconfigure it every time and is not very pratical to use it in this wayThe text was updated successfully, but these errors were encountered: