Bug 1087741 - signals 1, 17 and 27 not passed to container using docker attach --sig-proxy
Summary: signals 1, 17 and 27 not passed to container using docker attach --sig-proxy
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: docker-io
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lokesh Mandvekar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-15 08:10 UTC by Lukáš Doktor
Modified: 2014-07-01 23:00 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-05 07:56:17 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lukáš Doktor 2014-04-15 08:10:26 UTC
Description of problem:
When I send signals 1, 17, 27 to the `docker attach` process, which is running with --sig-proxy=true, it's not forwarded. Other signals are...

Version-Release number of selected component (if applicable):
docker-io-0.9.1-1.fc21.x86_64

How reproducible:
always

Steps to Reproduce:
1. docker -D run --detach=true --tty=false --sig-proxy=true --name test_BnHj localhost:5000/ldoktor/fedora:latest bash -c 'echo "STARTED"; for NUM in `seq 1 64`; do trap "echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done'
2. docker -D attach --sig-proxy=true test_BnHj
3. ps ax |grep docker
4. kill -1 $PID

Actual results:
(nothing)

Expected results:
Received 1, ignoring...

Additional info:
When you send any other signal (apart from 19, 9 and the mentioned ones) it works fine.

Comment 1 Lukáš Doktor 2014-04-15 08:41:34 UTC
OK, it's not always, but most of the time... (I successfully received the SIGHUP once)

Comment 2 Lukáš Doktor 2014-05-05 07:56:17 UTC
This works fine with docker-io-0.10.0-2.fc20.x86_64 and upstream dc9c28f/0.10.0.


Note You need to log in before you can comment on or make changes to this bug.