docker-compose volumes not works
I have this docker-compose.yml
client:
build:
context: ./client
dockerfile: Dockerfile
ports:
- "80:80"
- "443:443"
volumes:
- /etc/letsencrypt:/etc/letsencrypt
Also I have nginx.conf that is supposed to be proxy to client. Everything is good. Also I've set up ssl on host nginx - that is working as expected.
Now I want to use ssl in client-prox-nginx - it's inside docker.
I've copied nginx generated from certbot to docker nginx and it is not working.
So - with same nginx setup as host, docker nginx is not encrypting with ssl. I suspect that it is because docker can't access letsencrypt folder. Are "volumes" in docker-compose correct? How can I test that?
I know that nginx.conf is correct - it is copy of nginx.conf from host that is working perfectly.
Simply put - docker can't access localhost files. I used volumes and it not working.
docker nginx docker-compose
asked Nov 22 '18 at 20:19
Piotr MPiotr M
1403418
add a comment |
I have this docker-compose.yml
client:
build:
context: ./client
dockerfile: Dockerfile
ports:
- "80:80"
- "443:443"
volumes:
- /etc/letsencrypt:/etc/letsencrypt
Also I have nginx.conf that is supposed to be proxy to client. Everything is good. Also I've set up ssl on host nginx - that is working as expected.
Now I want to use ssl in client-prox-nginx - it's inside docker.
I've copied nginx generated from certbot to docker nginx and it is not working.
So - with same nginx setup as host, docker nginx is not encrypting with ssl. I suspect that it is because docker can't access letsencrypt folder. Are "volumes" in docker-compose correct? How can I test that?
I know that nginx.conf is correct - it is copy of nginx.conf from host that is working perfectly.
Simply put - docker can't access localhost files. I used volumes and it not working.
docker nginx docker-compose
asked Nov 22 '18 at 20:19
Piotr MPiotr M
1403418
Did you connect to the container to see if the volume works?
– night-gold
Nov 22 '18 at 21:08
That's the part of the question. How can I do that?
– Piotr M
Nov 22 '18 at 21:24
1
You could try to docker exec inside the container... full command being docker exec -ti <containerID> /bin/bash or sh at the end...
– night-gold
Nov 22 '18 at 21:35
This question is very confusing
– George Appleton
Nov 22 '18 at 21:35
I've updated the question George
– Piotr M
Nov 22 '18 at 21:39
add a comment |
I have this docker-compose.yml
client:
build:
context: ./client
dockerfile: Dockerfile
ports:
- "80:80"
- "443:443"
volumes:
- /etc/letsencrypt:/etc/letsencrypt
Also I have nginx.conf that is supposed to be proxy to client. Everything is good. Also I've set up ssl on host nginx - that is working as expected.
Now I want to use ssl in client-prox-nginx - it's inside docker.
I've copied nginx generated from certbot to docker nginx and it is not working.
So - with same nginx setup as host, docker nginx is not encrypting with ssl. I suspect that it is because docker can't access letsencrypt folder. Are "volumes" in docker-compose correct? How can I test that?
I know that nginx.conf is correct - it is copy of nginx.conf from host that is working perfectly.
Simply put - docker can't access localhost files. I used volumes and it not working.
docker nginx docker-compose
asked Nov 22 '18 at 20:19
Piotr MPiotr M
1403418
I have this docker-compose.yml
client:
build:
context: ./client
dockerfile: Dockerfile
ports:
- "80:80"
- "443:443"
volumes:
- /etc/letsencrypt:/etc/letsencrypt
Also I have nginx.conf that is supposed to be proxy to client. Everything is good. Also I've set up ssl on host nginx - that is working as expected.
Now I want to use ssl in client-prox-nginx - it's inside docker.
I've copied nginx generated from certbot to docker nginx and it is not working.
So - with same nginx setup as host, docker nginx is not encrypting with ssl. I suspect that it is because docker can't access letsencrypt folder. Are "volumes" in docker-compose correct? How can I test that?
I know that nginx.conf is correct - it is copy of nginx.conf from host that is working perfectly.
Simply put - docker can't access localhost files. I used volumes and it not working.
docker nginx docker-compose
docker nginx docker-compose
asked Nov 22 '18 at 20:19
Piotr MPiotr M
1403418
asked Nov 22 '18 at 20:19
Piotr MPiotr M
1403418
edited Nov 22 '18 at 21:39
Piotr M
asked Nov 22 '18 at 20:19
Piotr MPiotr M
1403418
asked Nov 22 '18 at 20:19
Piotr MPiotr M
1403418
asked Nov 22 '18 at 20:19
Piotr MPiotr M
1403418
1403418
Did you connect to the container to see if the volume works?
– night-gold
Nov 22 '18 at 21:08
That's the part of the question. How can I do that?
– Piotr M
Nov 22 '18 at 21:24
1
You could try to docker exec inside the container... full command being docker exec -ti <containerID> /bin/bash or sh at the end...
– night-gold
Nov 22 '18 at 21:35
This question is very confusing
– George Appleton
Nov 22 '18 at 21:35
I've updated the question George
– Piotr M
Nov 22 '18 at 21:39
add a comment |
Did you connect to the container to see if the volume works?
– night-gold
Nov 22 '18 at 21:08
That's the part of the question. How can I do that?
– Piotr M
Nov 22 '18 at 21:24
1
You could try to docker exec inside the container... full command being docker exec -ti <containerID> /bin/bash or sh at the end...
– night-gold
Nov 22 '18 at 21:35
This question is very confusing
– George Appleton
Nov 22 '18 at 21:35
I've updated the question George
– Piotr M
Nov 22 '18 at 21:39
Did you connect to the container to see if the volume works?
– night-gold
Nov 22 '18 at 21:08
Did you connect to the container to see if the volume works?
– night-gold
Nov 22 '18 at 21:08
That's the part of the question. How can I do that?
– Piotr M
Nov 22 '18 at 21:24
That's the part of the question. How can I do that?
– Piotr M
Nov 22 '18 at 21:24
1
1
You could try to docker exec inside the container... full command being docker exec -ti <containerID> /bin/bash or sh at the end...
– night-gold
Nov 22 '18 at 21:35
You could try to docker exec inside the container... full command being docker exec -ti <containerID> /bin/bash or sh at the end...
– night-gold
Nov 22 '18 at 21:35
This question is very confusing
– George Appleton
Nov 22 '18 at 21:35
This question is very confusing
– George Appleton
Nov 22 '18 at 21:35
I've updated the question George
– Piotr M
Nov 22 '18 at 21:39
I've updated the question George
– Piotr M
Nov 22 '18 at 21:39
add a comment |
1 Answer
1
active
oldest
votes
So per night-gold comment, I've connected to container. Files (ssl certs) are accessible from there.
But still ssl is not working. I will post another question. Hosts are working as expected, I'm layman in docker.
answered Nov 22 '18 at 21:48
Piotr MPiotr M
1403418
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437574%2fdocker-compose-volumes-not-works%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
So per night-gold comment, I've connected to container. Files (ssl certs) are accessible from there.
But still ssl is not working. I will post another question. Hosts are working as expected, I'm layman in docker.
answered Nov 22 '18 at 21:48
Piotr MPiotr M
1403418
add a comment |
So per night-gold comment, I've connected to container. Files (ssl certs) are accessible from there.
But still ssl is not working. I will post another question. Hosts are working as expected, I'm layman in docker.
answered Nov 22 '18 at 21:48
Piotr MPiotr M
1403418
add a comment |
So per night-gold comment, I've connected to container. Files (ssl certs) are accessible from there.
But still ssl is not working. I will post another question. Hosts are working as expected, I'm layman in docker.
answered Nov 22 '18 at 21:48
Piotr MPiotr M
1403418
So per night-gold comment, I've connected to container. Files (ssl certs) are accessible from there.
But still ssl is not working. I will post another question. Hosts are working as expected, I'm layman in docker.
answered Nov 22 '18 at 21:48
Piotr MPiotr M
1403418
answered Nov 22 '18 at 21:48
Piotr MPiotr M
1403418
answered Nov 22 '18 at 21:48
Piotr MPiotr M
1403418
answered Nov 22 '18 at 21:48
Piotr MPiotr M
1403418
1403418
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437574%2fdocker-compose-volumes-not-works%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you connect to the container to see if the volume works?
– night-gold
Nov 22 '18 at 21:08
That's the part of the question. How can I do that?
– Piotr M
Nov 22 '18 at 21:24
1
You could try to docker exec inside the container... full command being docker exec -ti <containerID> /bin/bash or sh at the end...
– night-gold
Nov 22 '18 at 21:35
This question is very confusing
– George Appleton
Nov 22 '18 at 21:35
I've updated the question George
– Piotr M
Nov 22 '18 at 21:39