when reading docker events, how to quit docker events instead of entire program?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
The requirement is inside a big while loop, given a specific docker container ID, I need to monitor the docker stop event using docker event command. When I found the event, I need to quit the docker event read.
The simplified bash script I wrote is as follows:
#! /bin/bash
while true
do
## other logics
docker events --filter='container=...' --filter='event=stop' | while read event
do
echo $event
break
done
echo "got here"
## other logics
done
So in one bash session, I would run this script, in another bash session, I would type the following command:
docker container stop cassandra-1
The problem is when I execute this bash program, I can capture the stop event, and print the event, but this command will read event repeated. How to quit the docker events and print "got here" ?
I've spent lots of time searching solution online, but can't find any good approach. I once considered using break, but it doesn't work, and I also considered kill -9 $$, but I will quit the entire script program. But I only need to quit the docker event instead of big while loop.
any good advice? Thanks so much!
bash docker break
edited Nov 24 '18 at 0:44
Cyrus
47.3k43881
asked Nov 23 '18 at 23:45
Shu LiuShu Liu
1
add a comment |
The requirement is inside a big while loop, given a specific docker container ID, I need to monitor the docker stop event using docker event command. When I found the event, I need to quit the docker event read.
The simplified bash script I wrote is as follows:
#! /bin/bash
while true
do
## other logics
docker events --filter='container=...' --filter='event=stop' | while read event
do
echo $event
break
done
echo "got here"
## other logics
done
So in one bash session, I would run this script, in another bash session, I would type the following command:
docker container stop cassandra-1
The problem is when I execute this bash program, I can capture the stop event, and print the event, but this command will read event repeated. How to quit the docker events and print "got here" ?
I've spent lots of time searching solution online, but can't find any good approach. I once considered using break, but it doesn't work, and I also considered kill -9 $$, but I will quit the entire script program. But I only need to quit the docker event instead of big while loop.
any good advice? Thanks so much!
bash docker break
edited Nov 24 '18 at 0:44
Cyrus
47.3k43881
asked Nov 23 '18 at 23:45
Shu LiuShu Liu
1
Replacebreakwithbreak 2?
– Cyrus
Nov 24 '18 at 0:32
Thanks Cyrus. Replace break with break 2 cannot work. I found the solution. Key point is to know how docker event command actually work. Based on my research, docker event will generate a process and stuck in the foreground process. You should CTRL+C to quit (refer to: docs.docker.com/engine/reference/commandline/events). So you can not use break to get out of it. The approach is to execute docker event command in the background job and kill it when I found the event.
– Shu Liu
Nov 24 '18 at 1:33
add a comment |
The requirement is inside a big while loop, given a specific docker container ID, I need to monitor the docker stop event using docker event command. When I found the event, I need to quit the docker event read.
The simplified bash script I wrote is as follows:
#! /bin/bash
while true
do
## other logics
docker events --filter='container=...' --filter='event=stop' | while read event
do
echo $event
break
done
echo "got here"
## other logics
done
So in one bash session, I would run this script, in another bash session, I would type the following command:
docker container stop cassandra-1
The problem is when I execute this bash program, I can capture the stop event, and print the event, but this command will read event repeated. How to quit the docker events and print "got here" ?
I've spent lots of time searching solution online, but can't find any good approach. I once considered using break, but it doesn't work, and I also considered kill -9 $$, but I will quit the entire script program. But I only need to quit the docker event instead of big while loop.
any good advice? Thanks so much!
bash docker break
edited Nov 24 '18 at 0:44
Cyrus
47.3k43881
asked Nov 23 '18 at 23:45
Shu LiuShu Liu
1
The requirement is inside a big while loop, given a specific docker container ID, I need to monitor the docker stop event using docker event command. When I found the event, I need to quit the docker event read.
The simplified bash script I wrote is as follows:
#! /bin/bash
while true
do
## other logics
docker events --filter='container=...' --filter='event=stop' | while read event
do
echo $event
break
done
echo "got here"
## other logics
done
So in one bash session, I would run this script, in another bash session, I would type the following command:
docker container stop cassandra-1
The problem is when I execute this bash program, I can capture the stop event, and print the event, but this command will read event repeated. How to quit the docker events and print "got here" ?
I've spent lots of time searching solution online, but can't find any good approach. I once considered using break, but it doesn't work, and I also considered kill -9 $$, but I will quit the entire script program. But I only need to quit the docker event instead of big while loop.
any good advice? Thanks so much!
bash docker break
bash docker break
edited Nov 24 '18 at 0:44
Cyrus
47.3k43881
asked Nov 23 '18 at 23:45
Shu LiuShu Liu
1
edited Nov 24 '18 at 0:44
Cyrus
47.3k43881
asked Nov 23 '18 at 23:45
Shu LiuShu Liu
1
edited Nov 24 '18 at 0:44
Cyrus
47.3k43881
edited Nov 24 '18 at 0:44
Cyrus
47.3k43881
edited Nov 24 '18 at 0:44
Cyrus
47.3k43881
47.3k43881
asked Nov 23 '18 at 23:45
Shu LiuShu Liu
1
asked Nov 23 '18 at 23:45
Shu LiuShu Liu
1
asked Nov 23 '18 at 23:45
Shu LiuShu Liu
1
1
Replacebreakwithbreak 2?
– Cyrus
Nov 24 '18 at 0:32
Thanks Cyrus. Replace break with break 2 cannot work. I found the solution. Key point is to know how docker event command actually work. Based on my research, docker event will generate a process and stuck in the foreground process. You should CTRL+C to quit (refer to: docs.docker.com/engine/reference/commandline/events). So you can not use break to get out of it. The approach is to execute docker event command in the background job and kill it when I found the event.
– Shu Liu
Nov 24 '18 at 1:33
add a comment |
Replacebreakwithbreak 2?
– Cyrus
Nov 24 '18 at 0:32
Thanks Cyrus. Replace break with break 2 cannot work. I found the solution. Key point is to know how docker event command actually work. Based on my research, docker event will generate a process and stuck in the foreground process. You should CTRL+C to quit (refer to: docs.docker.com/engine/reference/commandline/events). So you can not use break to get out of it. The approach is to execute docker event command in the background job and kill it when I found the event.
– Shu Liu
Nov 24 '18 at 1:33
Replace
break with break 2?– Cyrus
Nov 24 '18 at 0:32
Replace
break with break 2?– Cyrus
Nov 24 '18 at 0:32
Thanks Cyrus. Replace break with break 2 cannot work. I found the solution. Key point is to know how docker event command actually work. Based on my research, docker event will generate a process and stuck in the foreground process. You should CTRL+C to quit (refer to: docs.docker.com/engine/reference/commandline/events). So you can not use break to get out of it. The approach is to execute docker event command in the background job and kill it when I found the event.
– Shu Liu
Nov 24 '18 at 1:33
Thanks Cyrus. Replace break with break 2 cannot work. I found the solution. Key point is to know how docker event command actually work. Based on my research, docker event will generate a process and stuck in the foreground process. You should CTRL+C to quit (refer to: docs.docker.com/engine/reference/commandline/events). So you can not use break to get out of it. The approach is to execute docker event command in the background job and kill it when I found the event.
– Shu Liu
Nov 24 '18 at 1:33
add a comment |
1 Answer
1
active
oldest
votes
I found the solution. Key point is to know how docker event command actually work. Based on my research, docker event will generate a process and stuck in the foreground process. You should CTRL+C to quit (refer to: https://docs.docker.com/engine/reference/commandline/events). So you can not use break to get out of it. The approach is to execute docker event command in the background job and kill it when I found the event.
the code is as follows:
(docker events --filter 'container='"$container_id"'' --filter 'event=stop' &) | while read event
do
# kill this backgroud process
pkill -f "docker event.*stop"
done
answered Nov 24 '18 at 1:38
Shu LiuShu Liu
1
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%2f53453967%2fwhen-reading-docker-events-how-to-quit-docker-events-instead-of-entire-program%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
I found the solution. Key point is to know how docker event command actually work. Based on my research, docker event will generate a process and stuck in the foreground process. You should CTRL+C to quit (refer to: https://docs.docker.com/engine/reference/commandline/events). So you can not use break to get out of it. The approach is to execute docker event command in the background job and kill it when I found the event.
the code is as follows:
(docker events --filter 'container='"$container_id"'' --filter 'event=stop' &) | while read event
do
# kill this backgroud process
pkill -f "docker event.*stop"
done
answered Nov 24 '18 at 1:38
Shu LiuShu Liu
1
add a comment |
I found the solution. Key point is to know how docker event command actually work. Based on my research, docker event will generate a process and stuck in the foreground process. You should CTRL+C to quit (refer to: https://docs.docker.com/engine/reference/commandline/events). So you can not use break to get out of it. The approach is to execute docker event command in the background job and kill it when I found the event.
the code is as follows:
(docker events --filter 'container='"$container_id"'' --filter 'event=stop' &) | while read event
do
# kill this backgroud process
pkill -f "docker event.*stop"
done
answered Nov 24 '18 at 1:38
Shu LiuShu Liu
1
add a comment |
I found the solution. Key point is to know how docker event command actually work. Based on my research, docker event will generate a process and stuck in the foreground process. You should CTRL+C to quit (refer to: https://docs.docker.com/engine/reference/commandline/events). So you can not use break to get out of it. The approach is to execute docker event command in the background job and kill it when I found the event.
the code is as follows:
(docker events --filter 'container='"$container_id"'' --filter 'event=stop' &) | while read event
do
# kill this backgroud process
pkill -f "docker event.*stop"
done
answered Nov 24 '18 at 1:38
Shu LiuShu Liu
1
I found the solution. Key point is to know how docker event command actually work. Based on my research, docker event will generate a process and stuck in the foreground process. You should CTRL+C to quit (refer to: https://docs.docker.com/engine/reference/commandline/events). So you can not use break to get out of it. The approach is to execute docker event command in the background job and kill it when I found the event.
the code is as follows:
(docker events --filter 'container='"$container_id"'' --filter 'event=stop' &) | while read event
do
# kill this backgroud process
pkill -f "docker event.*stop"
done
answered Nov 24 '18 at 1:38
Shu LiuShu Liu
1
answered Nov 24 '18 at 1:38
Shu LiuShu Liu
1
answered Nov 24 '18 at 1:38
Shu LiuShu Liu
1
answered Nov 24 '18 at 1:38
Shu LiuShu Liu
1
1
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%2f53453967%2fwhen-reading-docker-events-how-to-quit-docker-events-instead-of-entire-program%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
Replace
breakwithbreak 2?– Cyrus
Nov 24 '18 at 0:32
Thanks Cyrus. Replace break with break 2 cannot work. I found the solution. Key point is to know how docker event command actually work. Based on my research, docker event will generate a process and stuck in the foreground process. You should CTRL+C to quit (refer to: docs.docker.com/engine/reference/commandline/events). So you can not use break to get out of it. The approach is to execute docker event command in the background job and kill it when I found the event.
– Shu Liu
Nov 24 '18 at 1:33