[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 1174354] New: Missing Requires: cadvisor
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1174354
Bug ID: 1174354
Summary: Missing Requires: cadvisor
Product: Fedora
Version: 21
Component: kubernetes
Assignee: jchaloup(a)redhat.com
Reporter: tstclair(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eparis(a)redhat.com, golang(a)lists.fedoraproject.org,
jchaloup(a)redhat.com, lsm5(a)redhat.com,
nhorman(a)redhat.com, vbatts(a)redhat.com
Description of problem:
k8's has a missing run-time dependency on cadvisor that is not installed when
k8's is installed.
Version-Release number of selected component (if applicable):
0.6-4.0.git993ef88.fc21
How reproducible:
100%
Steps to Reproduce:
1. yum install kubernetes
2. check installation list
Actual results:
no cadvisor
Expected results:
install cadvisor
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 4 months
[Bug 1135152] New: user: Current not implemented on linux/amd64
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1135152
Bug ID: 1135152
Summary: user: Current not implemented on linux/amd64
Product: Fedora
Version: 20
Component: golang
Assignee: vbatts(a)redhat.com
Reporter: adam(a)spicenitz.org
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lemenkov(a)gmail.com, lsm5(a)fedoraproject.org,
renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
golang seems to be using some cross-compiled components which are causing
problems. Specifically, Fedora has exactly the problem described here:
http://stackoverflow.com/questions/20609415/cross-compiling-user-current-...
Here is the sample code from that page:
package main
import (
"fmt"
"os/user"
)
func main() {
fmt.Println(user.Current())
}
You can build the sample code and see the problem directly:
$ go build ./current.go
$ ./current
<nil> user: Current not implemented on linux/amd64
Version-Release number of selected component (if applicable):
golang-1.2.2-22.fc20.x86_64
How reproducible:
Always
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 4 months
[Bug 1195525] New: Docker socket permissions prevent Cockpit integration
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1195525
Bug ID: 1195525
Summary: Docker socket permissions prevent Cockpit integration
Product: Fedora
Version: 21
Component: docker-io
Severity: medium
Assignee: lsm5(a)redhat.com
Reporter: Benjamin(a)BGRoberts.id.au
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,
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
Description of problem:
The removal of docker.socket and the docker user/group mean that docker cannot
be used as part of the cockpit console anymore (using non-root accounts). This
is because, although users can be added to the dockerroot group, the
permissions of the sockets are reset upon docker restart.
Version-Release number of selected component (if applicable):
docker-io-1.5.0-1.fc21.x86_64
cockpit-0.27-3.fc21.x86_64 / cockpit-head
Steps to Reproduce:
1. Add user to dockerroot
2. chown docker socket to root:dockerroot
3. Call a docker command from user (succeeds from CLI and cockpit)
4. restart docker
5. Call a docker command from user (fails from CLI and cockpit)
Actual results:
Ownership of docker socket are reset to root:root
Expected results:
Ownership of docker socket should be configurable and compatible with cockpit
Additional info:
related to https://bugzilla.redhat.com/show_bug.cgi?id=1192848
Relevant change in the rpm spec:
"* Fri Jan 16 2015 Lokesh Mandvekar <lsm5(a)fedoraproject.org> - 1.4.1-7
- docker group no longer used or created
- no socket activation
- config file updates to include info about docker_transition_unconfined
boolean"
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 6 months
[Bug 1166611] New: Extend golang %files section with golang.org/x directory ownership
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1166611
Bug ID: 1166611
Summary: Extend golang %files section with golang.org/x
directory ownership
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, lsm5(a)fedoraproject.org,
renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com
Description of problem:
https://groups.google.com/forum/#!topic/golang-nuts/eD8dh3T9yyA
First post:
...
This list shows the current base import paths, and their new equivalents.
code.google.com/p/go.benchmarks -> golang.org/x/benchmarks
code.google.com/p/go.blog -> golang.org/x/blog
code.google.com/p/go.crypto -> golang.org/x/crypto
code.google.com/p/go.exp -> golang.org/x/exp
code.google.com/p/go.image -> golang.org/x/image
code.google.com/p/go.mobile -> golang.org/x/mobile
code.google.com/p/go.net -> golang.org/x/net
code.google.com/p/go.sys -> golang.org/x/sys
code.google.com/p/go.talks -> golang.org/x/talks
code.google.com/p/go.text -> golang.org/x/text
code.google.com/p/go.tools -> golang.org/x/tools
...
import paths are being extended for new equivalents starting with
"golang.org/x/..."
Version-Release number of selected component (if applicable):
golang-1.3.99-2.1.4rc1.fc22
How reproducible:
Always
Steps to Reproduce:
1. rpm -q --provides golang | grep golang.org
Actual results:
Empty result
Expected results:
/usr/share/gocode/src/golang.org
/usr/share/gocode/src/golang.org/x
Additional info:
Extend ownership for all branches (at least el6, f20,f21,master)
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 6 months
[Bug 1187077] New: Fedora:latest docker image yum won't update
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1187077
Bug ID: 1187077
Summary: Fedora:latest docker image yum won't update
Product: Fedora
Version: 21
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: cyborg101010(a)gmail.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,
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
Description of problem:
I cannot install from or update yum inside Docker.
RUN yum install make automake gcc gcc-c++ kernel-devel tar wget
---> Running in 04cdfe47b7ac
One of the configured repositories failed (Fedora 21 - x86_64),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the
problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable fedora
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=fedora.skip_if_unavailable=true
Cannot retrieve metalink for repository: fedora/21/x86_64. Please verify its
path and try again
Version-Release number of selected component (if applicable):
Docker 1.4.1
Fedora:latest
How reproducible:
Seems rare, but I can find others with the issue (e.g.
https://registry.hub.docker.com/_/fedora/ see comment from crackcomm)
Steps to Reproduce:
1. Take any examples https://github.com/fedora-cloud/Fedora-Dockerfiles
2. docker build an example
3. Wait for yum update / install
Actual results:
Yum errors and exits.
Expected results:
Yum update / install
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1161618] New: influxdb: please update to 0.8.5
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1161618
Bug ID: 1161618
Summary: influxdb: please update to 0.8.5
Product: Fedora
Version: rawhide
Component: golang-github-influxdb-influxdb
Assignee: jchaloup(a)redhat.com
Reporter: ruben(a)rubenkerkhof.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, jchaloup(a)redhat.com,
lsm5(a)fedoraproject.org, vbatts(a)redhat.com
Thanks for packaging influxdb!
Would it be possible to upgrade the package to 0.8.5? It contains some fixes
regarding sharding I bumped in to, and also the new collectd plugin would be
nice to have.
Kind regards,
Ruben
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1119282] New: [Regression] Unable to run docker client as non-root user
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1119282
Bug ID: 1119282
Summary: [Regression] Unable to run docker client as non-root
user
Product: Fedora
Version: 19
Component: docker-io
Assignee: lsm5(a)switzerlandmail.ch
Reporter: psavage(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, lsm5(a)switzerlandmail.ch,
mattdm(a)redhat.com, mgoldman(a)redhat.com, s(a)shk.io,
vbatts(a)redhat.com
Description of problem: Docker used to be able to run it's client as non-root
user, allowed things like `docker ps` and `docker run` but since latest update
I am unable to do that. Even though the user running the docker command is in
the docker group, which previously worked.
Version-Release number of selected component (if
applicable):docker-io-1.0.0-6.fc19.x86_64
How reproducible:
Steps to Reproduce:
1. Run docker ps
2.
3.
Actual results:
2014/07/14 13:25:33 Get http:///var/run/docker.sock/v1.12/containers/json: dial
unix /var/run/docker.sock: permission denied
Expected results:
Docker command should run
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1144636] New: Docker fails to start on systems with SELinux and btrfs
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1144636
Bug ID: 1144636
Summary: Docker fails to start on systems with SELinux and
btrfs
Product: Fedora
Version: 20
Component: docker-io
Severity: urgent
Assignee: lsm5(a)fedoraproject.org
Reporter: voxadam(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
hushan.jia(a)gmail.com, jperrin(a)centos.org,
lsm5(a)fedoraproject.org, mattdm(a)redhat.com,
mgoldman(a)redhat.com, s(a)shk.io, thrcka(a)redhat.com,
vbatts(a)redhat.com
External Bug ID: Red Hat Bugzilla 1128041
External Bug ID: Red Hat Bugzilla 1128041
Description of problem:
The Docker daemon fails to start on systems with SELinux and btrfs
Version-Release number of selected component (if applicable):
Kernel: 3.16.2-200.fc20.x86_64 #1 SMP
Docker: 1.2.0 (2.fc20)
libselinux: 2.2.1 (6.fc20)
How reproducible:
Incredibly so.
Steps to Reproduce:
1. Install F20 on btrfs
2. systemctl start docker
3. Bang head against desk
Actual results:
adam@dekatron ~/bin sudo systemctl start docker
[sudo] password for adam:
Job for docker.service failed. See 'systemctl status docker.service' and
'journalctl -xn' for details.
✘ adam@dekatron ~/bin journalctl -xn
-- Logs begin at Wed 2014-09-17 14:41:46 PDT, end at Fri 2014-09-19 18:18:26
PDT. --
Sep 19 18:18:18 dekatron.voxadam.com docker[7517]: 2014/09/19 18:18:18 SELinux
is not supported with the BTRFS graph driver!
Sep 19 18:18:18 dekatron.voxadam.com systemd[1]: docker.service: main process
exited, code=exited, status=1/FAILURE
Sep 19 18:18:18 dekatron.voxadam.com systemd[1]: Failed to start Docker
Application Container Engine.
-- Subject: Unit docker.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit docker.service has failed.
--
-- The result is failed.
Expected results:
Docker should start.
Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=1128041
https://github.com/docker/docker/issues/7952
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 7 months
[Bug 1192721] New: Fix debugging - fix runtime-gdb.py
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1192721
Bug ID: 1192721
Summary: Fix debugging - fix runtime-gdb.py
Product: Fedora
Version: rawhide
Component: golang
Assignee: vbatts(a)redhat.com
Reporter: jan.kratochvil(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: admiller(a)redhat.com, golang(a)lists.fedoraproject.org,
lemenkov(a)gmail.com, lsm5(a)redhat.com,
renich(a)woralelandia.com, s(a)shk.io, vbatts(a)redhat.com
Created attachment 991759
--> https://bugzilla.redhat.com/attachment.cgi?id=991759&action=edit
Fedora packaging + runtime-gdb.py fix
Description of problem:
Currently golang GDB support script is not loaded at all. Load it and fix its
obsolete parts.
Version-Release number of selected component (if applicable):
golang-1.4.1-1.fc22.x86_64
How reproducible:
Always.
Steps to Reproduce:
$ gdb golang-produced binary
(gdb) start
(gdb) info goroutines
(gdb) goroutine 4 bt
Actual results:
Undefined info command: "goroutines". Try "help info".
Expected results:
Loading Go Runtime support.
(gdb) start
[...]
(gdb) info goroutines
* 1 running fname=runtime.switchtoM faddr=0x437a60 &g=0xc208000120
2 runnable fname=runtime.forcegchelper faddr=0x412010 &g=0xc208000480
3 runnable fname=runtime.bgsweep faddr=0x40dcd0 &g=0xc2080005a0
4 runnable fname=runtime.runfinq faddr=0x40d3f0 &g=0xc2080006c0
(gdb) goroutine 4 bt
#0 runtime.runfinq () at /usr/lib/golang/src/runtime/malloc.go:712
#1 0x0000000000439ca1 in runtime.goexit () at
/usr/lib/golang/src/runtime/asm_amd64.s:2232
#2 0x0000000000000000 in ?? ()
Additional info:
Probably some interfaces pretty printer there also needs to be fixed.
Backtraces need to be fixed etc.
https://sourceware.org/gdb/wiki/GoDebugging
--
You are receiving this mail because:
You are on the CC list for the bug.
8 years, 8 months