From: Soares Chen <soares.chen@gmail.com>
To: zsh-workers@zsh.org
Subject: Zsh scripts leave defunct processes when running under docker exec
Date: Wed, 11 Feb 2015 12:43:47 +0800 [thread overview]
Message-ID: <CACUDQOE1y34_b_OF8g4kf7JJisyBc0T5Chr_E8xkZiyO_kTRGQ@mail.gmail.com> (raw)
This only happens when the script is running inside a shell spawned by
`docker exec`. When running under normal system and under `docker
run`, there is no defunct process.
This bug is first discovered when I run nvm in docker
(https://github.com/creationix/nvm/issues/650). It was then discovered
that Docker's nsenter did not properly handle the SIGCHLD signal
raised from zsh. (https://github.com/docker/libcontainer/pull/369)
Even though it is now been fixed by Docker, I am not sure why zsh
would cause this bug in the first place.
I have a test script at the end of this post and also share it on
https://gist.github.com/soareschen/240e49116c7f2632d179
Steps to reproduce:
# terminal 1
docker run -it --rm --name test-zsh ubuntu:latest /bin/bash
apt-get install zsh curl
curl https://gist.githubusercontent.com/soareschen/240e49116c7f2632d179/raw/0be67acefd8d18fd62bb181998996f9a5772dc64/docker-zsh-test.sh
> docker-zsh-test.sh
chmod +x docker-zsh-test.sh
./docker-zsh-test.sh
ps auxf # no defunct process
# terminal 2
docker exec -it test-zsh /bin/zsh
./docker-zsh-test.sh
ps auxf # sed and zsh shown as defunct processes
#!/bin/zsh
# docker-zsh-test.sh
if [[ "$(echo "the black cat was chased by the brown dog" | sed -e
's/cat/fox/g' | grep fox)" = "" ]]; then
echo "cat"
else
echo "fox"
fi
next reply other threads:[~2015-02-11 4:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 4:43 Soares Chen [this message]
2015-02-11 6:53 ` Bart Schaefer
2015-02-11 10:11 ` Peter Stephenson
2015-02-11 16:13 ` Bart Schaefer
2015-02-13 10:39 ` Daniel Shahaf
2015-02-14 18:58 ` Bart Schaefer
2015-02-15 14:03 ` Soares Chen
2015-02-15 18:20 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACUDQOE1y34_b_OF8g4kf7JJisyBc0T5Chr_E8xkZiyO_kTRGQ@mail.gmail.com \
--to=soares.chen@gmail.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).