https://bugzilla.redhat.com/show_bug.cgi?id=1184710
Bug ID: 1184710
Summary: dnsmasq needs to be restarted after reboot for dns to
work in a Docker container
Product: Fedora
Version: 21
Component: docker-io
Assignee: lsm5(a)redhat.com
Reporter: jshepherd(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,
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
External Bug ID: Red Hat Bugzilla 1128208
External Bug ID: Red Hat Bugzilla 1128208
Description of problem:
Docker replies on dnsmasq to have 'listen-address' set to the docker bridge,
and have bind-interfaces option turned on. However in this configuration
dnsmasq has to start after docker in order for DNS to work in a docker
container.
Version-Release number of selected component (if applicable):
docker-io 1.4.0
dnsmasq 2.72
How reproducible:
Reboot the system with docker, and dnsmasq enabled.
Steps to Reproduce:
1. Ensure docker is using the default dns option of 172.17.42.1
2. Use the attached dnsmasq.conf
3. Reboot the system
4. Launch a docker container:
`docker run -i -t centos /usr/bin/ping www.redhat.com`
Actual results:
Cannot resolve hostname
Expected results:
Response from 'akamai' or similar
Additional info:
See related issue #1128208
I tried added a systemd 'After' for dnsmasq on docker.service, but it doesn't
seem to be honoured by systemd.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1108349
Bug ID: 1108349
Summary: remove golang-github-syndtr-gocapability from epel7
Product: Fedora EPEL
Version: epel7
Component: golang-github-syndtr-gocapability
Assignee: vbatts(a)redhat.com
Reporter: lsm5(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
remove this package from epel7 as it's now available in rhel7 proper.
Version-Release number of selected component (if applicable):
golang-github-syndtr-gocapability-0-0.5.git3454319.el7
Additional info:
retired from dist-git:
http://pkgs.fedoraproject.org/cgit/golang-github-syndtr-gocapability.git/tr…
For pkgdb, Vincent could you run this for the epel7 branch (I'm not an admin
for this one):
pkgdb-cli orphan --retire golang-github-syndtr-gocapability epel7
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1108337
Bug ID: 1108337
Summary: remove golang-googlecode-sqlite from epel7
Product: Fedora EPEL
Version: epel7
Component: golang-googlecode-sqlite
Assignee: lsm5(a)redhat.com
Reporter: lsm5(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
vbatts(a)redhat.com
Description of problem:
this package should be removed from epel7 as it's now available in rhel7 proper
Version-Release number of selected component (if applicable):
golang-googlecode-sqlite-0-0.9.hg74691fb6f837.el7
Additional info:
retired from dist-git:
http://pkgs.fedoraproject.org/cgit/golang-googlecode-sqlite.git/tree/?h=epe…
orphaned in pkgdb:
https://admin.fedoraproject.org/pkgdb/package/golang-googlecode-sqlite/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1108270
Bug ID: 1108270
Summary: remove golang-googlecode-net from epel7
Product: Fedora EPEL
Version: epel7
Component: golang-googlecode-net
Assignee: lsm5(a)redhat.com
Reporter: lsm5(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, vbatts(a)redhat.com
Description of problem:
this package should be removed from epel7 as it's available in rhel7 proper
Version-Release number of selected component (if applicable):
golang-googlecode-net-0-0.13.hg84a4013f96e0.el7
Additional info:
epel7 orphaned:
https://admin.fedoraproject.org/pkgdb/package/golang-googlecode-net/
retired from dist-git:
http://pkgs.fedoraproject.org/cgit/golang-googlecode-net.git/tree/?h=epel7
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1108249
Bug ID: 1108249
Summary: remove golang-github-gorilla-mux from epel7
Product: Fedora EPEL
Version: epel7
Component: golang-github-gorilla-mux
Assignee: lsm5(a)redhat.com
Reporter: lsm5(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com, vbatts(a)redhat.com
Description of problem:
remove this package from epel7 as it exists in rhel7 proper
Version-Release number of selected component (if applicable):
golang-github-gorilla-mux-0-0.13.git136d54f.el7
Additional info:
retired from dist-git:
http://pkgs.fedoraproject.org/cgit/golang-github-gorilla-mux.git/tree/?h=ep…
orphaned in pkgdb:
https://admin.fedoraproject.org/pkgdb/package/golang-github-gorilla-mux/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1108248
Bug ID: 1108248
Summary: remove golang-github-gorilla-context from epel7
Product: Fedora EPEL
Version: epel7
Component: golang-github-gorilla-context
Assignee: lsm5(a)redhat.com
Reporter: lsm5(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com
Description of problem:
this package should be removed from epel7 as it exists in RHEL7 proper
Version-Release number of selected component (if applicable):
golang-github-gorilla-context-0-0.23.gitb06ed15.el7
Additional info:
retired from dist-git:
http://pkgs.fedoraproject.org/cgit/golang-github-gorilla-context.git/tree/?…
orphaned in pkgdb:
https://admin.fedoraproject.org/pkgdb/package/golang-github-gorilla-context/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1108244
Bug ID: 1108244
Summary: remove golang-github-kr-pty from epel7
Product: Fedora EPEL
Version: epel7
Component: golang-github-kr-pty
Assignee: lsm5(a)redhat.com
Reporter: lsm5(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com,
mattdm(a)redhat.com
Description of problem:
Remove this package from epel7 as exists in RHEL7 proper
Version-Release number of selected component (if applicable):
golang-github-kr-pty-0-0.19.git67e2db2.el7
Additional info:
retired from dist-git
http://pkgs.fedoraproject.org/cgit/golang-github-kr-pty.git/tree/?h=epel7
and orphaned from pkgdb
https://admin.fedoraproject.org/pkgdb/package/golang-github-kr-pty/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1100502
Bug ID: 1100502
Summary: golang-1.2.2-2 update breaks GOROOT path
Product: Fedora
Version: 20
Component: golang
Assignee: adam(a)spicenitz.org
Reporter: porjo38(a)yahoo.com.au
QA Contact: extras-qa(a)fedoraproject.org
CC: adam(a)spicenitz.org, 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
Since updating to golang-1.2.2-2, I get error "go: cannot find GOROOT
directory: /usr/lib64/golang" when trying to run a go program e.g. "go run
main.go"
Adding a symbolic link fixes the issue:
ln -s /usr/lib/golang/ /usr/lib64/golang
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1099732
Bug ID: 1099732
Summary: go install fails if cgo is used
Product: Fedora
Version: 20
Component: golang
Assignee: adam(a)spicenitz.org
Reporter: davidb(a)davidb.org
QA Contact: extras-qa(a)fedoraproject.org
CC: adam(a)spicenitz.org, 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 897821
--> https://bugzilla.redhat.com/attachment.cgi?id=897821&action=edit
Example program to provoke bug
Description of problem:
'go install' tries to compile runtime/cgo.a and install it in /usr/lib when the
source makes use of Cgo.
Version-Release number of selected component (if applicable):
golang-src-1.2.2-2.fc20.noarch
golang-1.2.2-2.fc20.x86_64
golang-pkg-linux-amd64-1.2.2-2.fc20.noarch
golang-pkg-bin-linux-amd64-1.2.2-2.fc20.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Create directory with src/bug1/hello.go containing the attached file.
2. GOPATH=$(PWD) /usr/bin/go install bug1
Actual results:
go install runtime/cgo: open /usr/lib/golang/pkg/linux_amd64/runtime/cgo.a:
permission denied
Expected results:
Produces bin/bug1, which when run prints hello world. This worked fine with
1.2.1 (before today's update).
Additional info:
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1096293
Bug ID: 1096293
Summary: `docker start` doesn't fail on started container
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, s(a)shk.io, vbatts(a)redhat.com
Depends On: 1090071
+++ This bug was initially created as a clone of Bug #1090071 +++
Description of problem:
On older (0.9) docker, the `docker start $running_container` failed. The new
0.10.2 version just prints the container name and proceeds.
Version-Release number of selected component (if applicable):
docker-0.10.0-8.el7.x86_64
docker-io-0.10.0-2.fc20.x86_64
How reproducible:
Always
Steps to Reproduce:
1. docker run -i -t -name test fedora bash
2. docker start test
Actual results:
[root@t530 ~]# docker start test
test
[root@t530 ~]# echo &?
0
Expected results:
[root@t530 ~]# docker start test
Error: Cannot start container test: The container
429d709bc86c037b09e9f74dfab40aa33dc19bcf3109daf3f5b2fbbd3c6df297 is already
running.
2014/04/22 15:29:28 Error: failed to start one or more containers
[root@t530 ~]# echo &?
1
--- Additional comment from Lukas Doktor on 2014-05-05 03:38:57 EDT ---
Upstream Docker version 0.10.0, build dc9c28f/0.10.0 has the same issue
(silently passes even thought the container was already running)
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1090071
[Bug 1090071] `docker start` doesn't fail on started container
--
You are receiving this mail because:
You are on the CC list for the bug.