Redis : Creating Server TCP listening socket *:6379: unable to bind socket, errno: 13
0
# develop.yml
redis:
image: redis
command: redis-server --requirepass 123
ports:
- '6379:6379'
expose:
- "6379
docker-compose -f develop.yml up redis shows:
docker-compose -f develop.yml up redis
Starting django-blog_redis_1 ... done
Attaching to django-blog_redis_1
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # Redis version=5.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # Configuration loaded
redis_1 | 1:M 16 Nov 2018 03:52:46.935 # Creating Server TCP listening socket *:6379: unable to bind socket, errno: 13
I check the port:
fuser -k -n tcp 6379
but nothing use 6379.
How can I solve it?
docker redis
asked Nov 16 '18 at 3:58
Qiao JasonQiao Jason
468
add a comment |
0
# develop.yml
redis:
image: redis
command: redis-server --requirepass 123
ports:
- '6379:6379'
expose:
- "6379
docker-compose -f develop.yml up redis shows:
docker-compose -f develop.yml up redis
Starting django-blog_redis_1 ... done
Attaching to django-blog_redis_1
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # Redis version=5.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # Configuration loaded
redis_1 | 1:M 16 Nov 2018 03:52:46.935 # Creating Server TCP listening socket *:6379: unable to bind socket, errno: 13
I check the port:
fuser -k -n tcp 6379
but nothing use 6379.
How can I solve it?
docker redis
asked Nov 16 '18 at 3:58
Qiao JasonQiao Jason
468
By chance do you have something else running on port 6379?
– R.A. Lucas
Nov 16 '18 at 4:01
@R.A.Lucas no, I even restart the system, nothing running on port 6379
– Qiao Jason
Nov 16 '18 at 4:04
add a comment |
0
0
0
# develop.yml
redis:
image: redis
command: redis-server --requirepass 123
ports:
- '6379:6379'
expose:
- "6379
docker-compose -f develop.yml up redis shows:
docker-compose -f develop.yml up redis
Starting django-blog_redis_1 ... done
Attaching to django-blog_redis_1
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # Redis version=5.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # Configuration loaded
redis_1 | 1:M 16 Nov 2018 03:52:46.935 # Creating Server TCP listening socket *:6379: unable to bind socket, errno: 13
I check the port:
fuser -k -n tcp 6379
but nothing use 6379.
How can I solve it?
docker redis
asked Nov 16 '18 at 3:58
Qiao JasonQiao Jason
468
# develop.yml
redis:
image: redis
command: redis-server --requirepass 123
ports:
- '6379:6379'
expose:
- "6379
docker-compose -f develop.yml up redis shows:
docker-compose -f develop.yml up redis
Starting django-blog_redis_1 ... done
Attaching to django-blog_redis_1
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # Redis version=5.0.1, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1 | 1:C 16 Nov 2018 03:52:46.935 # Configuration loaded
redis_1 | 1:M 16 Nov 2018 03:52:46.935 # Creating Server TCP listening socket *:6379: unable to bind socket, errno: 13
I check the port:
fuser -k -n tcp 6379
but nothing use 6379.
How can I solve it?
docker redis
docker redis
asked Nov 16 '18 at 3:58
Qiao JasonQiao Jason
468
asked Nov 16 '18 at 3:58
Qiao JasonQiao Jason
468
asked Nov 16 '18 at 3:58
Qiao JasonQiao Jason
468
asked Nov 16 '18 at 3:58
Qiao JasonQiao Jason
468
asked Nov 16 '18 at 3:58
Qiao JasonQiao Jason
468
468
By chance do you have something else running on port 6379?
– R.A. Lucas
Nov 16 '18 at 4:01
@R.A.Lucas no, I even restart the system, nothing running on port 6379
– Qiao Jason
Nov 16 '18 at 4:04
add a comment |
By chance do you have something else running on port 6379?
– R.A. Lucas
Nov 16 '18 at 4:01
@R.A.Lucas no, I even restart the system, nothing running on port 6379
– Qiao Jason
Nov 16 '18 at 4:04
By chance do you have something else running on port 6379?
– R.A. Lucas
Nov 16 '18 at 4:01
By chance do you have something else running on port 6379?
– R.A. Lucas
Nov 16 '18 at 4:01
@R.A.Lucas no, I even restart the system, nothing running on port 6379
– Qiao Jason
Nov 16 '18 at 4:04
@R.A.Lucas no, I even restart the system, nothing running on port 6379
– Qiao Jason
Nov 16 '18 at 4:04
add a comment |
1 Answer
1
active
oldest
votes
1
My os: Deepin Linux.
It seems that the problem is with deepin.
Execute the following command to solve it:
sudo apt remove apparmor
Related discussion: https://github.com/docker/for-linux/issues/413
answered Nov 16 '18 at 6:52
Qiao JasonQiao Jason
468
1
@BMitch updated!
– Qiao Jason
Nov 16 '18 at 9:42
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');
});
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%2f53331231%2fredis-creating-server-tcp-listening-socket-6379-unable-to-bind-socket-errn%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
1
My os: Deepin Linux.
It seems that the problem is with deepin.
Execute the following command to solve it:
sudo apt remove apparmor
Related discussion: https://github.com/docker/for-linux/issues/413
answered Nov 16 '18 at 6:52
Qiao JasonQiao Jason
468
1
@BMitch updated!
– Qiao Jason
Nov 16 '18 at 9:42
add a comment |
1
My os: Deepin Linux.
It seems that the problem is with deepin.
Execute the following command to solve it:
sudo apt remove apparmor
Related discussion: https://github.com/docker/for-linux/issues/413
answered Nov 16 '18 at 6:52
Qiao JasonQiao Jason
468
1
@BMitch updated!
– Qiao Jason
Nov 16 '18 at 9:42
add a comment |
1
1
1
My os: Deepin Linux.
It seems that the problem is with deepin.
Execute the following command to solve it:
sudo apt remove apparmor
Related discussion: https://github.com/docker/for-linux/issues/413
answered Nov 16 '18 at 6:52
Qiao JasonQiao Jason
468
My os: Deepin Linux.
It seems that the problem is with deepin.
Execute the following command to solve it:
sudo apt remove apparmor
Related discussion: https://github.com/docker/for-linux/issues/413
answered Nov 16 '18 at 6:52
Qiao JasonQiao Jason
468
edited Nov 16 '18 at 9:42
answered Nov 16 '18 at 6:52
Qiao JasonQiao Jason
468
answered Nov 16 '18 at 6:52
Qiao JasonQiao Jason
468
answered Nov 16 '18 at 6:52
Qiao JasonQiao Jason
468
468
1
@BMitch updated!
– Qiao Jason
Nov 16 '18 at 9:42
add a comment |
1
@BMitch updated!
– Qiao Jason
Nov 16 '18 at 9:42
1
1
@BMitch updated!
– Qiao Jason
Nov 16 '18 at 9:42
@BMitch updated!
– Qiao Jason
Nov 16 '18 at 9:42
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');
});
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%2f53331231%2fredis-creating-server-tcp-listening-socket-6379-unable-to-bind-socket-errn%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
By chance do you have something else running on port 6379?
– R.A. Lucas
Nov 16 '18 at 4:01
@R.A.Lucas no, I even restart the system, nothing running on port 6379
– Qiao Jason
Nov 16 '18 at 4:04