Mongo docker image - unable to run on different port

-1

There are a tons of question here on SO citing how this command alone

docker run --name mymongo --network bridge -p 27117:27117 -v "$PWD/db":/data/db  -d mongo

should run mongo on port 27117.
However this doesn't work for me. The container runs, but the mongo is run on its default port alone (see output from container itself):

# mongo

MongoDB shell version v4.0.4

connecting to: mongodb://127.0.0.1:27017



# mongo --port 27117

MongoDB shell version v4.0.4

connecting to: mongodb://127.0.0.1:27117/

2018-11-20T17:26:09.345+0000 E QUERY    [js] Error: couldn't connect to server 127.0.0.1:27117, connection attempt failed: SocketException: Error connecting to 127.0.0.1:27117 :: caused by :: Connection refused :

What is going on?

Thanks a lot!

asked Nov 20 '18 at 17:26

JoeSlav

1,71522240

Could it be fire wall issue?

– kosa
Nov 20 '18 at 17:30

i'm trying from within the docker container, so no firewall there (i think)

– JoeSlav
Nov 20 '18 at 17:33

add a comment |

-1

There are a tons of question here on SO citing how this command alone

docker run --name mymongo --network bridge -p 27117:27117 -v "$PWD/db":/data/db  -d mongo

should run mongo on port 27117.
However this doesn't work for me. The container runs, but the mongo is run on its default port alone (see output from container itself):

# mongo

MongoDB shell version v4.0.4

connecting to: mongodb://127.0.0.1:27017



# mongo --port 27117

MongoDB shell version v4.0.4

connecting to: mongodb://127.0.0.1:27117/

2018-11-20T17:26:09.345+0000 E QUERY    [js] Error: couldn't connect to server 127.0.0.1:27117, connection attempt failed: SocketException: Error connecting to 127.0.0.1:27117 :: caused by :: Connection refused :

What is going on?

Thanks a lot!

asked Nov 20 '18 at 17:26

JoeSlav

1,71522240

Could it be fire wall issue?

– kosa
Nov 20 '18 at 17:30

i'm trying from within the docker container, so no firewall there (i think)

– JoeSlav
Nov 20 '18 at 17:33

add a comment |

-1

There are a tons of question here on SO citing how this command alone

docker run --name mymongo --network bridge -p 27117:27117 -v "$PWD/db":/data/db  -d mongo

should run mongo on port 27117.
However this doesn't work for me. The container runs, but the mongo is run on its default port alone (see output from container itself):

# mongo

MongoDB shell version v4.0.4

connecting to: mongodb://127.0.0.1:27017



# mongo --port 27117

MongoDB shell version v4.0.4

connecting to: mongodb://127.0.0.1:27117/

2018-11-20T17:26:09.345+0000 E QUERY    [js] Error: couldn't connect to server 127.0.0.1:27117, connection attempt failed: SocketException: Error connecting to 127.0.0.1:27117 :: caused by :: Connection refused :

What is going on?

Thanks a lot!

asked Nov 20 '18 at 17:26

JoeSlav

1,71522240

There are a tons of question here on SO citing how this command alone

docker run --name mymongo --network bridge -p 27117:27117 -v "$PWD/db":/data/db  -d mongo

should run mongo on port 27117.
However this doesn't work for me. The container runs, but the mongo is run on its default port alone (see output from container itself):

# mongo

MongoDB shell version v4.0.4

connecting to: mongodb://127.0.0.1:27017



# mongo --port 27117

MongoDB shell version v4.0.4

connecting to: mongodb://127.0.0.1:27117/

2018-11-20T17:26:09.345+0000 E QUERY    [js] Error: couldn't connect to server 127.0.0.1:27117, connection attempt failed: SocketException: Error connecting to 127.0.0.1:27117 :: caused by :: Connection refused :

What is going on?

Thanks a lot!

mongodb docker

asked Nov 20 '18 at 17:26

JoeSlav

1,71522240

asked Nov 20 '18 at 17:26

JoeSlav

1,71522240

asked Nov 20 '18 at 17:26

JoeSlav

1,71522240

asked Nov 20 '18 at 17:26

JoeSlav

1,71522240

asked Nov 20 '18 at 17:26

JoeSlav

1,71522240

Could it be fire wall issue?

– kosa
Nov 20 '18 at 17:30

i'm trying from within the docker container, so no firewall there (i think)

– JoeSlav
Nov 20 '18 at 17:33

add a comment |

Could it be fire wall issue?

– kosa
Nov 20 '18 at 17:30

i'm trying from within the docker container, so no firewall there (i think)

– JoeSlav
Nov 20 '18 at 17:33

Could it be fire wall issue?

– kosa
Nov 20 '18 at 17:30

i'm trying from within the docker container, so no firewall there (i think)

– JoeSlav
Nov 20 '18 at 17:33

add a comment |

2 Answers
2

active

oldest

votes

With that command you are telling docker that the port is 27117, but you also need to start mongo with that port.

To do so, just add --port 27117 at the end of your command:

docker run --name mymongo --network bridge -p 27117:27117 -v "$PWD/db":/data/db  -d mongo --port 27117

answered Nov 20 '18 at 17:59

Julio Daniel Reyes

2,082815

Thank you worked.

– JoeSlav
Nov 20 '18 at 18:13

add a comment |

Inside your container mongo runs on its default port, which is 27017

So, you should modify your command and specify the port mapping like this: -p 27117:27017

The full command would be this:

docker run --name mymongo --network bridge -p 27117:27017 -v "$PWD/db":/data/db  -d mongo

answered Nov 20 '18 at 18:05

Ciprian Stoica

1,11611219

Thank you. I thought the port:port was a range of ports to be opened, and not a port mapping :) always learn something!

– JoeSlav
Nov 20 '18 at 18:14

You're welcome. I'm glad it helped. :-)

– Ciprian Stoica
Nov 20 '18 at 18:15

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%2f53398370%2fmongo-docker-image-unable-to-run-on-different-port%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

With that command you are telling docker that the port is 27117, but you also need to start mongo with that port.

To do so, just add --port 27117 at the end of your command:

docker run --name mymongo --network bridge -p 27117:27117 -v "$PWD/db":/data/db  -d mongo --port 27117

answered Nov 20 '18 at 17:59

Julio Daniel Reyes

2,082815

Thank you worked.

– JoeSlav
Nov 20 '18 at 18:13

add a comment |

With that command you are telling docker that the port is 27117, but you also need to start mongo with that port.

To do so, just add --port 27117 at the end of your command:

docker run --name mymongo --network bridge -p 27117:27117 -v "$PWD/db":/data/db  -d mongo --port 27117

answered Nov 20 '18 at 17:59

Julio Daniel Reyes

2,082815

Thank you worked.

– JoeSlav
Nov 20 '18 at 18:13

add a comment |

With that command you are telling docker that the port is 27117, but you also need to start mongo with that port.

To do so, just add --port 27117 at the end of your command:

docker run --name mymongo --network bridge -p 27117:27117 -v "$PWD/db":/data/db  -d mongo --port 27117

answered Nov 20 '18 at 17:59

Julio Daniel Reyes

2,082815

With that command you are telling docker that the port is 27117, but you also need to start mongo with that port.

To do so, just add --port 27117 at the end of your command:

docker run --name mymongo --network bridge -p 27117:27117 -v "$PWD/db":/data/db  -d mongo --port 27117

answered Nov 20 '18 at 17:59

Julio Daniel Reyes

2,082815

answered Nov 20 '18 at 17:59

Julio Daniel Reyes

2,082815

answered Nov 20 '18 at 17:59

Julio Daniel Reyes

2,082815

answered Nov 20 '18 at 17:59

Julio Daniel Reyes

2,082815

Thank you worked.

– JoeSlav
Nov 20 '18 at 18:13

add a comment |

Thank you worked.

– JoeSlav
Nov 20 '18 at 18:13

Thank you worked.

– JoeSlav
Nov 20 '18 at 18:13

add a comment |

Inside your container mongo runs on its default port, which is 27017

So, you should modify your command and specify the port mapping like this: -p 27117:27017

The full command would be this:

docker run --name mymongo --network bridge -p 27117:27017 -v "$PWD/db":/data/db  -d mongo

answered Nov 20 '18 at 18:05

Ciprian Stoica

1,11611219

Thank you. I thought the port:port was a range of ports to be opened, and not a port mapping :) always learn something!

– JoeSlav
Nov 20 '18 at 18:14

You're welcome. I'm glad it helped. :-)

– Ciprian Stoica
Nov 20 '18 at 18:15

add a comment |

Inside your container mongo runs on its default port, which is 27017

So, you should modify your command and specify the port mapping like this: -p 27117:27017

The full command would be this:

docker run --name mymongo --network bridge -p 27117:27017 -v "$PWD/db":/data/db  -d mongo

answered Nov 20 '18 at 18:05

Ciprian Stoica

1,11611219

Thank you. I thought the port:port was a range of ports to be opened, and not a port mapping :) always learn something!

– JoeSlav
Nov 20 '18 at 18:14

You're welcome. I'm glad it helped. :-)

– Ciprian Stoica
Nov 20 '18 at 18:15

add a comment |

Inside your container mongo runs on its default port, which is 27017

So, you should modify your command and specify the port mapping like this: -p 27117:27017

The full command would be this:

docker run --name mymongo --network bridge -p 27117:27017 -v "$PWD/db":/data/db  -d mongo

answered Nov 20 '18 at 18:05

Ciprian Stoica

1,11611219

Inside your container mongo runs on its default port, which is 27017

So, you should modify your command and specify the port mapping like this: -p 27117:27017

The full command would be this:

docker run --name mymongo --network bridge -p 27117:27017 -v "$PWD/db":/data/db  -d mongo

answered Nov 20 '18 at 18:05

Ciprian Stoica

1,11611219

answered Nov 20 '18 at 18:05

Ciprian Stoica

1,11611219

answered Nov 20 '18 at 18:05

Ciprian Stoica

1,11611219

answered Nov 20 '18 at 18:05

Ciprian Stoica

1,11611219

Thank you. I thought the port:port was a range of ports to be opened, and not a port mapping :) always learn something!

– JoeSlav
Nov 20 '18 at 18:14

You're welcome. I'm glad it helped. :-)

– Ciprian Stoica
Nov 20 '18 at 18:15

add a comment |

Thank you. I thought the port:port was a range of ports to be opened, and not a port mapping :) always learn something!

– JoeSlav
Nov 20 '18 at 18:14

You're welcome. I'm glad it helped. :-)

– Ciprian Stoica
Nov 20 '18 at 18:15

Thank you. I thought the port:port was a range of ports to be opened, and not a port mapping :) always learn something!

– JoeSlav
Nov 20 '18 at 18:14

You're welcome. I'm glad it helped. :-)

– Ciprian Stoica
Nov 20 '18 at 18:15

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.

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

Search This Blog

Ufyukyu