-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Postgres container fails to launch #919
Comments
I have a same problem. My solution was add to docker-compose.yml file Like this:
|
Can confirm, I had this bug and the suggested addition fixes it |
I had the same issue also and the suggested edit to the Info:
|
helped - PGDATA=/tmp |
Setting PGDATA=/tmp worked for me as well! |
@FMate Thank you very much man. But, does it affect the our database persistence? |
I think it will affect the database persistence since everything is lost on reboot. |
Thanks @FMate but @eloyekunle and @SalahAdDin is right the data is not persistent on reboot everything is lost. does any one know better solution. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi again 👋 we would like to inform you that this issue has been automatically |
Info:
$ docker --version
): 17.03.1-ce, build c6d412e$ git rev-parse HEAD
): 0e0dc44Issue:
What seems to be going wrong?
With a fresh copy of laradock, the postgres container fails to launch.
Expected behavior:
What should be happening instead?
Self-explanatory
Reproduce:
How might we be able to reproduce the error?
docker-compose up -d postgres
Relevant Code:
Console output:
The text was updated successfully, but these errors were encountered: