[Bug 1096296] New: man page inaccuracy about --sig-proxy and --tty
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1096296
Bug ID: 1096296
Summary: man page inaccuracy about --sig-proxy and --tty
Product: Red Hat Enterprise Linux 7
Version: 7.1
Component: docker
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.com
QA Contact: virt-bugs(a)redhat.com
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, skottler(a)redhat.com,
vbatts(a)redhat.com, whenry(a)redhat.com
Depends On: 1087697
+++ This bug was initially created as a clone of Bug #1087697 +++
Description of problem:
Hi guys,
the man page states:
--sig-proxy=true: Proxify all received signal to the process (even
in non-tty mode)
But the real behavior is, that sig-proxy doesn't work when --tty=true. It
should be mentioned in there, taht --sig-proxy is incompatible with --tty.
Version-Release number of selected component (if applicable):
docker-io-0.9.1-1.fc21.x86_64
How reproducible:
always
Steps to Reproduce:
1. man docker
Actual results:
man page says it works even in non-tty
Expected results:
man page warns that --tty can't be used with --sig-proxy
How to verify:
1. docker run --tty=true -i --rm fedora bash -c 'for NUM in `seq 1 64`; do trap
"echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done'
2. ps -ax | grep docker
3. kill -SIGUSR1 $PID
4. (with --tty=true no signals are received, when you try the same with
--tty=false, signals are proxified and messages are displayed)
--- Additional comment from Lokesh Mandvekar on 2014-04-15 02:11:48 EDT ---
Copying William (he recently got per subcommand manpages merged upstream).
this seems to be the case even in the latest manpage (I'm guessing this was
inherited from the original manpage).
William, was there any discussion about this in your PR?
--- Additional comment from Lokesh Mandvekar on 2014-04-15 02:15:31 EDT ---
btw, the 0.10 rpm includes the latest manpages (should be in yum soon)
--- Additional comment from Lukas Doktor on 2014-04-15 04:45:55 EDT ---
Thanks for a quick reply. I tried the docker-io-0.10.0-2.fc20.x86_64 which
says:
--sig-proxy=true|false:
When set to true, proxify all received signals to the process
(even in non-tty mode). The default is true.
I'd really like to change it to "only in non-tty" with possible warning that
--tty=true is incompatible with --sig-proxy.
--- Additional comment from William Henry on 2014-04-30 15:54:25 EDT ---
I go this text from upstream. I'll check.
--- Additional comment from William Henry on 2014-04-30 16:02:22 EDT ---
Lukas,according to the folks upstream, this is a bug in docker run and attach.
It should be as the text suggests.
Can you file a bug upstream with docker? Here:
https://github.com/dotcloud/docker/issues
Please just take the information you posted above and post it there.
Thanks. Well spotted.
Best,
William
--- Additional comment from Lukas Doktor on 2014-05-02 04:02:01 EDT ---
Upstream tracer:
https://github.com/dotcloud/docker/issues/5547
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1087697
[Bug 1087697] man page inaccuracy about --sig-proxy and --tty
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 3 months
[Bug 1096276] New: signal 27 (SIGPROF) not passed to container using --sig-proxy
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1096276
Bug ID: 1096276
Summary: signal 27 (SIGPROF) not passed to container using
--sig-proxy
Product: Red Hat Enterprise Linux 7
Version: 7.1
Component: docker
Assignee: lsm5(a)redhat.com
Reporter: ldoktor(a)redhat.com
QA Contact: virt-bugs(a)redhat.com
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lsm5(a)redhat.com, mattdm(a)redhat.com,
mgoldman(a)redhat.com, skottler(a)redhat.com,
vbatts(a)redhat.com
Depends On: 1087720
+++ This bug was initially created as a clone of Bug #1087720 +++
Description of problem:
When I send signal 27 to the docker process, which is running with
--sig-proxy=true, it's not forwarded. Other signals are...
Version-Release number of selected component (if applicable):
docker-0.10.0-8.el7.x86_64
docker-io-0.9.1-1.fc21.x86_64
upstream Docker version 0.10.0, build dc9c28f/0.10.0
How reproducible:
always
Steps to Reproduce:
1. /usr/bin/docker -D run --tty=false --rm -i --name test_eoly
localhost:5000/ldoktor/fedora:latest bash -c 'for NUM in `seq 1 64`; do trap
"echo Received $NUM, ignoring..." $NUM; done; while :; do sleep 1; done'
2. ps ax |grep docker
3. kill -27 $PID
Actual results:
nothing
Expected results:
Received 27, ignoring...
Additional info:
When you send any other signal (apart from 19 or 9) it works fine.
--- Additional comment from Lukas Doktor on 2014-04-15 04:59:24 EDT ---
The signal 17 is also ignored.
--- Additional comment from Lukas Doktor on 2014-05-05 03:48:25 EDT ---
The same bug is in upstream Docker version 0.10.0, build dc9c28f/0.10.0
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1087720
[Bug 1087720] signal 27 (SIGPROF) not passed to container using --sig-proxy
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 3 months
[Bug 1250465] New: Tracker for golang-github-hashicorp-go-msgpack
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1250465
Bug ID: 1250465
Summary: Tracker for golang-github-hashicorp-go-msgpack
Product: Fedora
Version: rawhide
Component: golang-github-hashicorp-go-msgpack
Assignee: fpokorny(a)redhat.com
Reporter: fpokorny(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com
Tracker for async updates of golang-github-hashicorp-go-msgpack for rawhide and
other fedora distribution.
As golang devel packages are used only as a build-time dependency at the
moment, this tracker keeps updates and other information about this package,
e.g. broken dependencies, exceptions, important pieces of information and other
issues.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 3 months
[Bug 1250508] New: Tracker for golang-github-skynetservices-skydns
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1250508
Bug ID: 1250508
Summary: Tracker for golang-github-skynetservices-skydns
Product: Fedora
Version: rawhide
Component: golang-github-skynetservices-skydns
Assignee: fpokorny(a)redhat.com
Reporter: fpokorny(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com
Tracker for async updates of golang-github-skynetservices-skydns for rawhide
and other fedora distribution.
As golang devel packages are used only as a build-time dependency at the
moment, this tracker keeps updates and other information about this package,
e.g. broken dependencies, exceptions, important pieces of information and other
issues.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 3 months
[Bug 1269191] New: Skydns cannot bind to port 53
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1269191
Bug ID: 1269191
Summary: Skydns cannot bind to port 53
Product: Fedora
Version: 22
Component: golang-github-skynetservices-skydns
Assignee: fpokorny(a)redhat.com
Reporter: costan(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com
Description of problem:
By default, skydns runs under its own user, so it cannot bind to port 53.
Version-Release number of selected component (if applicable):
0.7.git6c94cbe.fc22
This is the version in updates-testing for Fedora 22. It seems like it needs
more karma to be promoted to stable.
How reproducible: always
Steps to Reproduce:
1. dnf install skydns
2. systemctl start skydns
3. systemctl status skydns
4. dig @127.0.0.1 skydns.local
Actual results:
skydns errors out because it can't bind to port 53.
I can't issue DNS queries.
Expected results: I should be able to issue DNS queries.
Additional info:
I worked around this problem by creating a systemd socket file, and using
socket activation. skydns supports this. I'll be happy to provide additional
details, if it helps. I think this is a good solution, as it avoids having to
run skydns as root.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 3 months
[Bug 1258166] New: Please remove macros.golang from golang
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1258166
Bug ID: 1258166
Summary: Please remove macros.golang from golang
Product: Fedora
Version: rawhide
Component: golang
Assignee: vbatts(a)redhat.com
Reporter: jchaloup(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lemenkov(a)gmail.com, renich(a)woralelandia.com, s(a)shk.io,
vbatts(a)redhat.com
Description of problem:
Macros from macros.golang (go_arches and gopath) are provided by
go-srpm-macros. Macros from go-srpm-macros support secondary architectures as
well and provide additional macros.
Please, remove macros.golang from golang for f22 and higher.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 3 months
[Bug 1250674] New: please build golang-googlecode-gcfg for epel7
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1250674
Bug ID: 1250674
Summary: please build golang-googlecode-gcfg for epel7
Product: Fedora EPEL
Version: epel7
Component: golang-googlecode-gcfg
Assignee: fpokorny(a)redhat.com
Reporter: carl.george(a)rackspace.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
I would like to see asciinema in epel7. The latest version requires this go
package. Please build it for epel7.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 3 months
[Bug 1247656] New: Tracker for golang-github-BurntSushi-toml
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1247656
Bug ID: 1247656
Summary: Tracker for golang-github-BurntSushi-toml
Product: Fedora
Version: rawhide
Component: golang-github-BurntSushi-toml
Severity: low
Priority: low
Assignee: fpokorny(a)redhat.com
Reporter: fpokorny(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fpokorny(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com,
vbatts(a)redhat.com
Tracker for async updates for rawhide and other fedora distribution.
As golang devel packages are used only as a build-time dependency at the
moment, this tracker keeps updates and other information about this package,
e.g. broken dependencies, exceptions, important pieces of information and other
issues.
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 4 months
[Bug 1217613] New: Cannot start container [8] System error: mountpoint for cpuset not found
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1217613
Bug ID: 1217613
Summary: Cannot start container [8] System error: mountpoint
for cpuset not found
Product: Fedora
Version: 21
Component: docker-io
Assignee: ichavero(a)redhat.com
Reporter: jiri.folta(a)centrum.cz
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, mgoldman(a)redhat.com,
miminar(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
Created attachment 1020711
--> https://bugzilla.redhat.com/attachment.cgi?id=1020711&action=edit
screenshot of the error
Description of problem:
when trying to run a container using Cockpit I get "System error: mountpoint
for cpuset not found" error
Version-Release number of selected component (if applicable):
cockpit:
Version 0.27.
Built on Wed Mar 25 12:53:20 UTC 2015.
How reproducible:
allways
Steps to Reproduce:
1.Install minimal Fedora 21 for arm platform from
http://www.digitaldreamtime.co.uk/images/Fidora/21/
2.update the system
3.install cockpit and docker
4.login to the server using web interface https://ip:9090
5.download Image: docker.io/wordpress:latest
6. try running the image
Actual results:
you get an error message(attached)
Expected results:
actually running the image
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 4 months
[Bug 1258822] New: The docker build command produces panic
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1258822
Bug ID: 1258822
Summary: The docker build command produces panic
Product: Fedora
Version: 21
Component: docker-io
Severity: high
Assignee: ichavero(a)redhat.com
Reporter: mfojtik(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: adimania(a)gmail.com, admiller(a)redhat.com,
golang(a)lists.fedoraproject.org, hushan.jia(a)gmail.com,
ichavero(a)redhat.com, jchaloup(a)redhat.com,
jperrin(a)centos.org, lsm5(a)redhat.com,
mgoldman(a)redhat.com, miminar(a)redhat.com, s(a)shk.io,
thrcka(a)redhat.com, vbatts(a)redhat.com,
wolfy(a)nobugconsulting.ro
Description of problem:
The `docker build` command panics. The command prints "" after few steps of the
docker build.
Client version: 1.7.1.fc21
Client API version: 1.19
Package Version (client): docker-io-1.7.1-3.git33de319.fc21.x86_64
Go version (client): go1.4.2
Git commit (client): 33de319/1.7.1
OS/Arch (client): linux/amd64
Cannot connect to the Docker daemon. Is 'docker -d' running on this host?
lease number of selected component (if applicable):
Steps to Reproduce:
1. git clone https://github.com/openshift/jenkins
2. cd jenkins
3. make build
Actual results:
Step 0 : FROM centos:centos7
---> 7322fbe74aa5
Step 1 : MAINTAINER Ben Parees <bparees(a)redhat.com>
---> Using cache
---> 15996a891236
Step 2 : ENV JENKINS_VERSION 1.609 HOME /var/lib/jenkins JENKINS_HOME
/var/lib/jenkins
---> Using cache
---> 53337e305e98
Step 3 : LABEL k8s.io.description "Jenkins is a continuous integration server"
k8s.io.display-name "Jenkins 1.609" openshift.io.expose-services "8080:http"
openshift.io.tags "jenkins,jenkins1,ci"
---> Using cache
---> 17d72d6b80b9
Step 4 : EXPOSE 8080 50000
---> Using cache
---> a8ffe929cb51
Step 5 : RUN curl http://pkg.jenkins-ci.org/redhat/jenkins.repo -o
/etc/yum.repos.d/jenkins.repo && rpm --import
http://pkg.jenkins-ci.org/redhat/jenkins-ci.org.key && yum install -y tar
zip unzip java-1.8.0-openjdk jenkins-1.609 && yum clean all && chmod
og+rw /var/lib/jenkins && curl -L
https://github.com/openshift/origin/releases/download/v1.0.2/openshift-or...
| tar -zx && mv oc /usr/local/bin && rm oadm && rm openshift
---> Running in 0455b7d5be68
unexpected EOF
Makefile:18: recipe for target 'build' failed
make: *** [build] Error 1
Interesting bits from the `journalctl -u docker`:
Sep 01 11:15:12 openshiftdev.local docker[1543]: 2015/09/01 11:15:12 http:
panic serving @: runtime error: slice bounds out of range
Sep 01 11:15:12 openshiftdev.local docker[1543]: goroutine 708 [running]:
Sep 01 11:15:12 openshiftdev.local docker[1543]: net/http.func·011()
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/usr/lib/golang/src/net/http/server.go:1130 +0xbb fp=0xc208a8ea40
sp=0xc208a8e960
Sep 01 11:15:12 openshiftdev.local docker[1543]: runtime.call16(0xc208a8fef0,
0xc20819c1b0, 0x0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/usr/lib/golang/src/runtime/asm_amd64.s:401 +0x45 fp=0xc208a8ea58
sp=0xc208a8ea40
Sep 01 11:15:12 openshiftdev.local docker[1543]: runtime.gopanic(0xb89f60,
0xc20802a010)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/usr/lib/golang/src/runtime/panic.go:387 +0x3a8 fp=0xc208a8eac0 sp=0xc208a8ea58
Sep 01 11:15:12 openshiftdev.local docker[1543]: runtime.panicslice()
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/usr/lib/golang/src/runtime/panic.go:18 +0x4e fp=0xc208a8eae8 sp=0xc208a8eac0
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/pkg/systemd.RegisterMachine(0xc20877da81, 0x13,
0xc208da8bc0, 0x40, 0x5acd, 0xc65450, 0x1, 0x0, 0x0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/pkg/systemd/register.go:33
+0x624 fp=0xc208a8ec28 sp=0xc208a8eae8
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/daemon.(*Container).registerMachine(0xc2080b34a0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/daemon/container_linux.go:1044
+0xa4 fp=0xc208a8ed00 sp=0xc208a8ec28
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/daemon.(*Container).waitForStart(0xc2080b34a0, 0x0,
0x0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/daemon/container.go:761
+0x2e6 fp=0xc208a8ee30 sp=0xc208a8ed00
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/daemon.(*Container).Start(0xc2080b34a0, 0x0, 0x0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/daemon/container.go:295
+0x4cd fp=0xc208a8ef40 sp=0xc208a8ee30
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/builder.(*Builder).run(0xc2089baf00, 0xc2080b34a0,
0x0, 0x0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/builder/internals.go:605
+0x11b fp=0xc208a8f060 sp=0xc208a8ef40
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/builder.run(0xc2089baf00, 0xc208686c00, 0x3, 0x4, 0x0,
0xc2085e5c00, 0x1e6, 0x0, 0x0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/builder/dispatchers.go:348
+0x8d5 fp=0xc208a8f200 sp=0xc208a8f060
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/builder.(*Builder).dispatch(0xc2089baf00, 0x5,
0xc2084ddc80, 0x0, 0x0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/builder/evaluator.go:342
+0xdae fp=0xc208a8f418 sp=0xc208a8f200
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/builder.(*Builder).Run(0xc2089baf00, 0x7feff5f0e5c8,
0xc2086e6c70, 0x0, 0x0, 0x0, 0x0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/builder/evaluator.go:177
+0x4b5 fp=0xc208a8f598 sp=0xc208a8f418
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/builder.Build(0xc2080b42a0, 0xc208858410, 0x0, 0x0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/builder/job.go:174
+0x7f2 fp=0xc208a8f7b8 sp=0xc208a8f598
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/api/server.(*Server).postBuild(0xc2080fc3c0,
0xc2081289c7, 0x4, 0x7feff5ef6490, 0xc208695180, 0xc208858340, 0xc2087e5e30,
0x0, 0x0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/api/server/server.go:1346
+0xe99 fp=0xc208a8f990 sp=0xc208a8f7b8
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/api/server.*Server.(github.com/docker/docker/api...,
0x4, 0x7feff5ef6490, 0xc208695180, 0xc208858340, 0xc2087e5e30, 0x0, 0x0)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/api/server/server.go:1606
+0x7b fp=0xc208a8f9e0 sp=0xc208a8f990
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/docker/docker/api/server.func·008(0x7feff5ef6490, 0xc208695180,
0xc208858340)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/_build/src/github.com/docker/docker/api/server/server.go:1566
+0xacd fp=0xc208a8fb88 sp=0xc208a8f9e0
Sep 01 11:15:12 openshiftdev.local docker[1543]:
net/http.HandlerFunc.ServeHTTP(0xc2080fddc0, 0x7feff5ef6490, 0xc208695180,
0xc208858340)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/usr/lib/golang/src/net/http/server.go:1265 +0x41 fp=0xc208a8fba8
sp=0xc208a8fb88
Sep 01 11:15:12 openshiftdev.local docker[1543]:
github.com/gorilla/mux.(*Router).ServeHTTP(0xc208103270, 0x7feff5ef6490,
0xc208695180, 0xc208858340)
Sep 01 11:15:12 openshiftdev.local docker[1543]:
/builddir/build/BUILD/docker-33de3192f50bc95ecd3b9583ce5a1ad65000c470/vendor/src/github.com/gorilla/mux/mux.go:98
+0x297 fp=0xc208a8fcb0 sp=0xc208a8fba8
Expected results:
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 4 months