starting postgres container with persistant volume [docker compose]

I have a problem with my database container, so I want to mount an existant database(from host) to the generated container (with docker-compose). I will show you the important part of the yaml file :

postgres:

        image: postgres

        environment:

            POSTGRES_USER: user

            POSTGRES_PASSWORD: pass

        ports:

        - "5432:5432"

        volumes:

        - ./postgres/data:/var/lib/postgresql/data

So, when I build and turn on docker-compose, postgres container exited:

enter image description here

If I remove the persistant volume, it wokrs ! I have also tested with mysql, mongodb -> same issue.

Could you light me up ?

Thanks.

edited Nov 20 '18 at 10:07

asked Nov 16 '18 at 16:40

wolfgunner

247

2

First thing to do is to check the logs (docker logs <container-id>). There may be something interesting to explain what's happening there. Otherwise, I usually try to run the image using a shell and then try to figure out what's wrong. In this case, you could run docker run -v data:/var/lib/postgresql/data -p 5432:5432 -e POSTGRES_USER=user -e POSTGRES_PASSWORD=pass --rm -it postgres bash From there you can try to start the postgres daemon just as if docker were not involved, and at that point your question becomes a postgres question (rather than a docker one).
– Stephen Crosby
Nov 16 '18 at 16:50

Thanks for your contribution, I have just shared the way out of this problem.
– wolfgunner
Nov 20 '18 at 11:19

add a comment |

I have a problem with my database container, so I want to mount an existant database(from host) to the generated container (with docker-compose). I will show you the important part of the yaml file :

postgres:

        image: postgres

        environment:

            POSTGRES_USER: user

            POSTGRES_PASSWORD: pass

        ports:

        - "5432:5432"

        volumes:

        - ./postgres/data:/var/lib/postgresql/data

So, when I build and turn on docker-compose, postgres container exited:

enter image description here

If I remove the persistant volume, it wokrs ! I have also tested with mysql, mongodb -> same issue.

Could you light me up ?

Thanks.

edited Nov 20 '18 at 10:07

asked Nov 16 '18 at 16:40

wolfgunner

247

2

First thing to do is to check the logs (docker logs <container-id>). There may be something interesting to explain what's happening there. Otherwise, I usually try to run the image using a shell and then try to figure out what's wrong. In this case, you could run docker run -v data:/var/lib/postgresql/data -p 5432:5432 -e POSTGRES_USER=user -e POSTGRES_PASSWORD=pass --rm -it postgres bash From there you can try to start the postgres daemon just as if docker were not involved, and at that point your question becomes a postgres question (rather than a docker one).
– Stephen Crosby
Nov 16 '18 at 16:50

Thanks for your contribution, I have just shared the way out of this problem.
– wolfgunner
Nov 20 '18 at 11:19

add a comment |

I have a problem with my database container, so I want to mount an existant database(from host) to the generated container (with docker-compose). I will show you the important part of the yaml file :

postgres:

        image: postgres

        environment:

            POSTGRES_USER: user

            POSTGRES_PASSWORD: pass

        ports:

        - "5432:5432"

        volumes:

        - ./postgres/data:/var/lib/postgresql/data

So, when I build and turn on docker-compose, postgres container exited:

enter image description here

If I remove the persistant volume, it wokrs ! I have also tested with mysql, mongodb -> same issue.

Could you light me up ?

Thanks.

edited Nov 20 '18 at 10:07

asked Nov 16 '18 at 16:40

wolfgunner

247

I have a problem with my database container, so I want to mount an existant database(from host) to the generated container (with docker-compose). I will show you the important part of the yaml file :

postgres:

        image: postgres

        environment:

            POSTGRES_USER: user

            POSTGRES_PASSWORD: pass

        ports:

        - "5432:5432"

        volumes:

        - ./postgres/data:/var/lib/postgresql/data

So, when I build and turn on docker-compose, postgres container exited:

enter image description here

If I remove the persistant volume, it wokrs ! I have also tested with mysql, mongodb -> same issue.

Could you light me up ?

Thanks.

postgresql docker docker-compose

edited Nov 20 '18 at 10:07

asked Nov 16 '18 at 16:40

wolfgunner

247

edited Nov 20 '18 at 10:07

asked Nov 16 '18 at 16:40

wolfgunner

247

edited Nov 20 '18 at 10:07

asked Nov 16 '18 at 16:40

wolfgunner

247

asked Nov 16 '18 at 16:40

wolfgunner

247

asked Nov 16 '18 at 16:40

wolfgunner

247

2

First thing to do is to check the logs (docker logs <container-id>). There may be something interesting to explain what's happening there. Otherwise, I usually try to run the image using a shell and then try to figure out what's wrong. In this case, you could run docker run -v data:/var/lib/postgresql/data -p 5432:5432 -e POSTGRES_USER=user -e POSTGRES_PASSWORD=pass --rm -it postgres bash From there you can try to start the postgres daemon just as if docker were not involved, and at that point your question becomes a postgres question (rather than a docker one).
– Stephen Crosby
Nov 16 '18 at 16:50

Thanks for your contribution, I have just shared the way out of this problem.
– wolfgunner
Nov 20 '18 at 11:19

add a comment |

2

First thing to do is to check the logs (docker logs <container-id>). There may be something interesting to explain what's happening there. Otherwise, I usually try to run the image using a shell and then try to figure out what's wrong. In this case, you could run docker run -v data:/var/lib/postgresql/data -p 5432:5432 -e POSTGRES_USER=user -e POSTGRES_PASSWORD=pass --rm -it postgres bash From there you can try to start the postgres daemon just as if docker were not involved, and at that point your question becomes a postgres question (rather than a docker one).
– Stephen Crosby
Nov 16 '18 at 16:50

Thanks for your contribution, I have just shared the way out of this problem.
– wolfgunner
Nov 20 '18 at 11:19

First thing to do is to check the logs (docker logs <container-id>). There may be something interesting to explain what's happening there. Otherwise, I usually try to run the image using a shell and then try to figure out what's wrong. In this case, you could run

docker run -v data:/var/lib/postgresql/data -p 5432:5432 -e POSTGRES_USER=user -e POSTGRES_PASSWORD=pass --rm -it postgres bash

From there you can try to start the postgres daemon just as if docker were not involved, and at that point your question becomes a postgres question (rather than a docker one).
– Stephen Crosby
Nov 16 '18 at 16:50

docker run -v data:/var/lib/postgresql/data -p 5432:5432 -e POSTGRES_USER=user -e POSTGRES_PASSWORD=pass --rm -it postgres bash

Thanks for your contribution, I have just shared the way out of this problem.
– wolfgunner
Nov 20 '18 at 11:19

add a comment |

1 Answer
1

active

oldest

votes

I resolve this matter and I want to share it. In fact, for getting our container turns on after ' docker-compose up ' command, we should add tty and command arguments like :

postgres:

        image: postgres

        environment:

            POSTGRES_USER: user

            POSTGRES_PASSWORD: pass

        ports:

        - "5432:5432"

        volumes:

        - ./postgres/data:/var/lib/postgresql/data

        tty: true

        command: /bin/bash

I hope that would be useful.

answered Nov 20 '18 at 11:18

wolfgunner

247

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53342053%2fstarting-postgres-container-with-persistant-volume-docker-compose%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

I resolve this matter and I want to share it. In fact, for getting our container turns on after ' docker-compose up ' command, we should add tty and command arguments like :

postgres:

        image: postgres

        environment:

            POSTGRES_USER: user

            POSTGRES_PASSWORD: pass

        ports:

        - "5432:5432"

        volumes:

        - ./postgres/data:/var/lib/postgresql/data

        tty: true

        command: /bin/bash

I hope that would be useful.

answered Nov 20 '18 at 11:18

wolfgunner

247

add a comment |

I resolve this matter and I want to share it. In fact, for getting our container turns on after ' docker-compose up ' command, we should add tty and command arguments like :

postgres:

        image: postgres

        environment:

            POSTGRES_USER: user

            POSTGRES_PASSWORD: pass

        ports:

        - "5432:5432"

        volumes:

        - ./postgres/data:/var/lib/postgresql/data

        tty: true

        command: /bin/bash

I hope that would be useful.

answered Nov 20 '18 at 11:18

wolfgunner

247

add a comment |

I resolve this matter and I want to share it. In fact, for getting our container turns on after ' docker-compose up ' command, we should add tty and command arguments like :

postgres:

        image: postgres

        environment:

            POSTGRES_USER: user

            POSTGRES_PASSWORD: pass

        ports:

        - "5432:5432"

        volumes:

        - ./postgres/data:/var/lib/postgresql/data

        tty: true

        command: /bin/bash

I hope that would be useful.

answered Nov 20 '18 at 11:18

wolfgunner

247

I resolve this matter and I want to share it. In fact, for getting our container turns on after ' docker-compose up ' command, we should add tty and command arguments like :

postgres:

        image: postgres

        environment:

            POSTGRES_USER: user

            POSTGRES_PASSWORD: pass

        ports:

        - "5432:5432"

        volumes:

        - ./postgres/data:/var/lib/postgresql/data

        tty: true

        command: /bin/bash

I hope that would be useful.

answered Nov 20 '18 at 11:18

wolfgunner

247

answered Nov 20 '18 at 11:18

wolfgunner

247

answered Nov 20 '18 at 11:18

wolfgunner

247

answered Nov 20 '18 at 11:18

wolfgunner

247

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

Some of your past answers have not been well-received, and you're in danger of being blocked from answering.

Please pay close attention to the following guidance:

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Cfrgtkky