Why docker-compose containers cannot be reach?
I have installed images on aws(t2.micro),
have the following docker-compose:
version: "3"
services:
eureka:
image: voipp/eurekaserver
ports:
- "8888:8888"
configserver:
image: voipp/configserver
ports:
- "8761:8761"
I have all images installed on a server, and call docker-compose up.
Docker starts my containers, but I cannot reach them from my PC!
Help me figure it out, plz.
PS. When I start images just by command docker run -p ... everything works fine(apps are approacheable), but docker-compose doesn't work as expected(
UPD: ports are opened in aws, how else i can reach em simply after docker run -p...
UPD2: If i start my app without container, it really is able to reach outer 8761 port
docker
asked Nov 20 '18 at 20:57
voippvoipp
19612
add a comment |
I have installed images on aws(t2.micro),
have the following docker-compose:
version: "3"
services:
eureka:
image: voipp/eurekaserver
ports:
- "8888:8888"
configserver:
image: voipp/configserver
ports:
- "8761:8761"
I have all images installed on a server, and call docker-compose up.
Docker starts my containers, but I cannot reach them from my PC!
Help me figure it out, plz.
PS. When I start images just by command docker run -p ... everything works fine(apps are approacheable), but docker-compose doesn't work as expected(
UPD: ports are opened in aws, how else i can reach em simply after docker run -p...
UPD2: If i start my app without container, it really is able to reach outer 8761 port
docker
asked Nov 20 '18 at 20:57
voippvoipp
19612
Did you open up AWS security groups on those ports, 8888 & 8761?
– kosa
Nov 20 '18 at 20:59
@kosa yeah, because i can reach em after docker run -p...
– voipp
Nov 20 '18 at 21:02
@kosa the problem somehow related to container. My app, stated inside container cannot reach outer 8761 port. But, when i start app without container, it really able to reach outer 8761 port
– voipp
Nov 21 '18 at 7:46
add a comment |
I have installed images on aws(t2.micro),
have the following docker-compose:
version: "3"
services:
eureka:
image: voipp/eurekaserver
ports:
- "8888:8888"
configserver:
image: voipp/configserver
ports:
- "8761:8761"
I have all images installed on a server, and call docker-compose up.
Docker starts my containers, but I cannot reach them from my PC!
Help me figure it out, plz.
PS. When I start images just by command docker run -p ... everything works fine(apps are approacheable), but docker-compose doesn't work as expected(
UPD: ports are opened in aws, how else i can reach em simply after docker run -p...
UPD2: If i start my app without container, it really is able to reach outer 8761 port
docker
asked Nov 20 '18 at 20:57
voippvoipp
19612
I have installed images on aws(t2.micro),
have the following docker-compose:
version: "3"
services:
eureka:
image: voipp/eurekaserver
ports:
- "8888:8888"
configserver:
image: voipp/configserver
ports:
- "8761:8761"
I have all images installed on a server, and call docker-compose up.
Docker starts my containers, but I cannot reach them from my PC!
Help me figure it out, plz.
PS. When I start images just by command docker run -p ... everything works fine(apps are approacheable), but docker-compose doesn't work as expected(
UPD: ports are opened in aws, how else i can reach em simply after docker run -p...
UPD2: If i start my app without container, it really is able to reach outer 8761 port
docker
docker
asked Nov 20 '18 at 20:57
voippvoipp
19612
asked Nov 20 '18 at 20:57
voippvoipp
19612
edited Nov 21 '18 at 7:48
voipp
asked Nov 20 '18 at 20:57
voippvoipp
19612
asked Nov 20 '18 at 20:57
voippvoipp
19612
asked Nov 20 '18 at 20:57
voippvoipp
19612
19612
Did you open up AWS security groups on those ports, 8888 & 8761?
– kosa
Nov 20 '18 at 20:59
@kosa yeah, because i can reach em after docker run -p...
– voipp
Nov 20 '18 at 21:02
@kosa the problem somehow related to container. My app, stated inside container cannot reach outer 8761 port. But, when i start app without container, it really able to reach outer 8761 port
– voipp
Nov 21 '18 at 7:46
add a comment |
Did you open up AWS security groups on those ports, 8888 & 8761?
– kosa
Nov 20 '18 at 20:59
@kosa yeah, because i can reach em after docker run -p...
– voipp
Nov 20 '18 at 21:02
@kosa the problem somehow related to container. My app, stated inside container cannot reach outer 8761 port. But, when i start app without container, it really able to reach outer 8761 port
– voipp
Nov 21 '18 at 7:46
Did you open up AWS security groups on those ports, 8888 & 8761?
– kosa
Nov 20 '18 at 20:59
Did you open up AWS security groups on those ports, 8888 & 8761?
– kosa
Nov 20 '18 at 20:59
@kosa yeah, because i can reach em after docker run -p...
– voipp
Nov 20 '18 at 21:02
@kosa yeah, because i can reach em after docker run -p...
– voipp
Nov 20 '18 at 21:02
@kosa the problem somehow related to container. My app, stated inside container cannot reach outer 8761 port. But, when i start app without container, it really able to reach outer 8761 port
– voipp
Nov 21 '18 at 7:46
@kosa the problem somehow related to container. My app, stated inside container cannot reach outer 8761 port. But, when i start app without container, it really able to reach outer 8761 port
– voipp
Nov 21 '18 at 7:46
add a comment |
1 Answer
1
active
oldest
votes
The answer is the container calls on its inner localhost, not remote containers .
answered Nov 21 '18 at 22:41
voippvoipp
19612
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%2f53401417%2fwhy-docker-compose-containers-cannot-be-reach%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
The answer is the container calls on its inner localhost, not remote containers .
answered Nov 21 '18 at 22:41
voippvoipp
19612
add a comment |
The answer is the container calls on its inner localhost, not remote containers .
answered Nov 21 '18 at 22:41
voippvoipp
19612
add a comment |
The answer is the container calls on its inner localhost, not remote containers .
answered Nov 21 '18 at 22:41
voippvoipp
19612
The answer is the container calls on its inner localhost, not remote containers .
answered Nov 21 '18 at 22:41
voippvoipp
19612
answered Nov 21 '18 at 22:41
voippvoipp
19612
answered Nov 21 '18 at 22:41
voippvoipp
19612
answered Nov 21 '18 at 22:41
voippvoipp
19612
19612
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%2f53401417%2fwhy-docker-compose-containers-cannot-be-reach%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 open up AWS security groups on those ports, 8888 & 8761?
– kosa
Nov 20 '18 at 20:59
@kosa yeah, because i can reach em after docker run -p...
– voipp
Nov 20 '18 at 21:02
@kosa the problem somehow related to container. My app, stated inside container cannot reach outer 8761 port. But, when i start app without container, it really able to reach outer 8761 port
– voipp
Nov 21 '18 at 7:46