-
Notifications
You must be signed in to change notification settings - Fork 143
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
Question about "/var/lib/postgresql/data" volume #53
Comments
This volume is created by the parent docker image (the official postgresql docker image). |
Strange, here is a detailed view from portainer: I named the volume in my compose so when i look at it i know what it is. From my compose:
|
Please read the docker files I attach here. This project imports the official postgresql docker image, and this last docker image is the one that creates the volume you are asking. But this repository makes no use of the volume you are asking, it only uses the postgresql cli programs, don't start any postgresql server. |
Thanks. So it's normal to have that volume in this image. Correct? |
Yes, it it will never be used. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hi, have a little question.
I have actually this compose file:
I checked performing a manually backup and it works.
I just don't understand why a new volume is created with the container, pointing to
/var/lib/postgresql/data
. In my compose file i called the volumepgbackups_data
just to recognize it.Thank you in advance!
The text was updated successfully, but these errors were encountered: