golang November 2013

golang@lists.fedoraproject.org

12 participants
215 discussions

[Bug 1033606] New: Failed to connect to network from Docker container
by Red Hat Bugzilla 17 Jun '15

17 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1033606 Bug ID: 1033606 Summary: Failed to connect to network from Docker container Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: mfojtik(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, vbatts(a)redhat.com Description of problem: Connecting to external network from Docker container fail due to firewalld. I guess you must have masquerade enabled, however this is not mentioned anywhere. I think docker-io should set the firewalld rules automatically, or tell users that they need to enable masquarade in firewalld. Version-Release number of selected component (if applicable): Name : docker-io Arch : x86_64 Version : 0.7 Release : 0.17.rc6.fc20 Steps to Reproduce: 1. $ yum install docker-io 2. $ systemctl enable docker.service 3. $ systemctl start docker.service 4. $ docker pull mattdm/fedora 5. $ docker run -i -t mattdm/fedora:latest /bin/bash 6. $ ping google.com ping: unknown host google.com When I stop firewalld on host (systemctl stop firewalld) and then restart the docker (systemctl restart docker), the ping works like a charm. Actual results: Unable to connect outside the Docker container with firewalld enabled. Expected results: Docker should configure firewalld automatically (during install?), or inform users to do so manually. Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 68

[Bug 1033604] New: Unable to start systemd service in Docker container
by Red Hat Bugzilla 19 May '15

19 May '15

https://bugzilla.redhat.com/show_bug.cgi?id=1033604 Bug ID: 1033604 Summary: Unable to start systemd service in Docker container Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: mfojtik(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, vbatts(a)redhat.com Description of problem: Using Dockerfile like this: FROM mattdm/fedora:latest RUN yum update -y RUN yum install -y redis RUN systemctl enable redis.service RUN systemctl start redis.service EXPOSE 6379 ENTRYPOINT ["/usr/bin/redis-cli"] The step 'systemctl start redis.service' failed with this error message: Failed to get D-Bus connection: No connection to service manager. Version-Release number of selected component (if applicable): Name : docker-io Arch : x86_64 Version : 0.7 Release : 0.17.rc6.fc20 Steps to Reproduce: 1. Save the above Dockerfile 2. Run: docker build -t test/redis . 3. The build fill faile on systemctl start. Actual results: The service failed to start due to D-BUS connection. Expected results: The service should be started? Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 33

[Bug 1029587] New: upgrade to go1.2 (once it is available)
by Red Hat Bugzilla 19 Feb '15

19 Feb '15

https://bugzilla.redhat.com/show_bug.cgi?id=1029587 Bug ID: 1029587 Summary: upgrade to go1.2 (once it is available) Product: Fedora Version: rawhide Component: golang Severity: low Assignee: adam(a)spicenitz.org Reporter: vbatts(a)redhat.com 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, vbatts(a)redhat.com What steps will reproduce the problem? If possible, include a link to a program on play.golang.org. 1. export GOPATH=$(mktemp -d) 2. go get code.google.com/p/go.tools/cmd/oracle 3. What is the expected output? What do you see instead? /tmp/tmp.cjYFzAeLWC/src/code.google.com/p/go.tools/importer/source.go:434: n.Lparen undefined (type *ast.TypeAssertExpr has no field or method Lparen) /tmp/tmp.cjYFzAeLWC/src/code.google.com/p/go.tools/importer/source.go:435: n.Lparen undefined (type *ast.TypeAssertExpr has no field or method Lparen) /tmp/tmp.cjYFzAeLWC/src/code.google.com/p/go.tools/importer/source.go:436: n.Rparen undefined (type *ast.TypeAssertExpr has no field or method Rparen) Which compiler are you using (5g, 6g, 8g, gccgo)? 6g Which operating system are you using? Red Hat Enterprise Linux Workstation release 6.4 (Santiago) Which version are you using? go version go1.1.2 linux/amd64 (golang-1.1.2-4.el6.x86_64) Please provide any additional information below. I tested against the tip of their repo (future version 1.2) (go version devel +39c724dd7f25 Tue Nov 12 09:28:07 2013 +1100 linux/amd64) and code.google.com/p/go.tools/cmd/oracle and code.google.com/p/go.tools/cmd/ssadump build just fine -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1035304] New: Error when starting a container: cannot unmarshal bool into Go value of type string
by Red Hat Bugzilla 28 May '14

28 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1035304 Bug ID: 1035304 Summary: Error when starting a container: cannot unmarshal bool into Go value of type string Product: Fedora EPEL Version: el6 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: mgoldman(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: accept4(7, 0xc2001be540, [112], SOCK_CLOEXEC|SOCK_NONBLOCK) = -1 EAGAIN (Resource temporarily unavailable) read(9, "POST /v1.7/containers/create HTT"..., 4096) = 550 clock_gettime(CLOCK_REALTIME, {1385557957, 704016349}) = 0 clock_gettime(CLOCK_REALTIME, {1385557957, 704076878}) = 0 clock_gettime(CLOCK_REALTIME, {1385557957, 704218620}) = 0 write(2, "[debug] api.go:1008 Calling POST"..., 52[debug] api.go:1008 Calling POST /containers/create ) = 52 futex(0xd0bef8, FUTEX_WAIT, 0, NULL2013/11/27 14:12:37 POST /v1.7/containers/create [/var/lib/docker|237066b1] +job create() [/var/lib/docker|237066b1] -job create() = ERR (ExportEnv json: cannot unmarshal bool into Go value of type string) [error] api.go:1034 Error: create: ExportEnv json: cannot unmarshal bool into Go value of type string [error] api.go:82 HTTP Error: statusCode=500 create: ExportEnv json: cannot unmarshal bool into Go value of type string [debug] api.go:1008 Calling GET /images/json 2013/11/27 14:28:41 GET /v1.7/images/json This issue exists when running docker-io-0.7.0-2.el6.x86_64 (unreleased) as daemon with following flag: -b none. [root@centos64 ~]# docker -v Docker version 0.7.0, build 0d078b6/0.7.0 -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1034951] New: golang-vim has unsatisfied dependencies on epel6
by Red Hat Bugzilla 14 Jan '14

14 Jan '14

https://bugzilla.redhat.com/show_bug.cgi?id=1034951 Bug ID: 1034951 Summary: golang-vim has unsatisfied dependencies on epel6 Product: Fedora EPEL Version: el6 Component: golang Severity: high Assignee: admiller(a)redhat.com Reporter: tis(a)foobar.fi QA Contact: extras-qa(a)fedoraproject.org CC: adam(a)spicenitz.org, admiller(a)redhat.com, golang(a)lists.fedoraproject.org, lsm5(a)redhat.com package: golang-vim-1.1.2-7.el6.noarch from epel-testing unresolved deps: vim-filesystem vim-filesystem is post rhel6 and is not available so golang-vim is not installable. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 1022983] New: Consider updating Rawhide to Go 1.2 release candidate
by Red Hat Bugzilla 14 Jan '14

14 Jan '14

https://bugzilla.redhat.com/show_bug.cgi?id=1022983 Bug ID: 1022983 Summary: Consider updating Rawhide to Go 1.2 release candidate Product: Fedora Version: rawhide Component: golang Assignee: adam(a)spicenitz.org Reporter: mattdm(a)redhat.com 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, renich(a)woralelandia.com Go 1.2 is in code freeze, with a release date scheduled for December 1. Go 1.2 release candidate 2 was released last week: https://groups.google.com/forum/#!topic/Golang-Nuts/5enxY7gSLB4 I think we should update golang in Rawhide (but not F20 or F19) to the release candidate, so we can start testing builds against it and making any necessary adjustments. For docker's in-container init process, we need the go-net libs but we also want the binary to be static; this isn't possible in 1.1 but will be in 1.2. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=OrJBJhyrxQ&a=cc_unsubscribe

2 34

[Bug 1026545] New: dockerinit fails with "libdevmapper.so.1.02: cannot open shared object file"
by Red Hat Bugzilla 13 Dec '13

13 Dec '13

https://bugzilla.redhat.com/show_bug.cgi?id=1026545 Bug ID: 1026545 Summary: dockerinit fails with "libdevmapper.so.1.02: cannot open shared object file" Product: Fedora Version: 19 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: sjenning(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, vbatts(a)redhat.com Description of problem: dockerinit fails with "libdevmapper.so.1.02: cannot open shared object file" Version-Release number of selected component (if applicable): docker-io-0.7-0.12.dm.fc19.x86_64.rpm How reproducible: Every time Steps to Reproduce: 1. Install docker-io-0.7-0.12.dm.fc19.x86_64.rpm on F19 2. Download official ubuntu image 3. docker run ubuntu echo "hello world" Actual results: /.dockerinit: error while loading shared libraries: libdevmapper.so.1.02: cannot open shared object file: No such file or directory Expected results: Get "hello world" output from ubuntu container -- You are receiving this mail because: You are on the CC list for the bug.

1 50

[Bug 1036217] New: docker-io doesn't work without firewalld
by Red Hat Bugzilla 13 Dec '13

13 Dec '13

https://bugzilla.redhat.com/show_bug.cgi?id=1036217 Bug ID: 1036217 Summary: docker-io doesn't work without firewalld Product: Fedora Version: 19 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: m.a.young(a)durham.ac.uk QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, vbatts(a)redhat.com The recent changes to the docker.service systemd file won't work if firewalld isn't installed, and starts firewalld if it isn't running. This means a docker user is forced to use a particular firewall solution and can't choose to use alternate options. If this is really what is intended then the docker-io package should require the firewalld package. Otherwise I suggest you remove the Requires=firewalld.service line in the docker.service file or replace it with the weaker Wants=firewalld.service which will still try to start firewalld but doesn't block docker if it fails to start (eg. if it isn't installed). -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1034095] New: Hie devicemapper mounts in Gnome
by Red Hat Bugzilla 13 Dec '13

13 Dec '13

https://bugzilla.redhat.com/show_bug.cgi?id=1034095 Bug ID: 1034095 Summary: Hie devicemapper mounts in Gnome Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)redhat.com Reporter: mgoldman(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org CC: golang(a)lists.fedoraproject.org, lsm5(a)redhat.com, mattdm(a)redhat.com, mgoldman(a)redhat.com, vbatts(a)redhat.com Description of problem: If you use docker in a graphical environment, when you start a container - the mounted filesystem will be shown in Gnome Files explorer. I don't think there is any benefit in it - even more - there is some danger that we can unmount the filesystem by accident. I would like to see these filesystems hidden. I'm assigning this to docker-io component to get more opinions, later we can move it to Gnome if this will be accepted. -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1036027] New: Save daemon log to file
by Red Hat Bugzilla 13 Dec '13

13 Dec '13

https://bugzilla.redhat.com/show_bug.cgi?id=1036027 Bug ID: 1036027 Summary: Save daemon log to file Product: Fedora EPEL Version: el6 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: mgoldman(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 Created attachment 830533 --> https://bugzilla.redhat.com/attachment.cgi?id=830533&action=edit Patch that fixes this issue Description of problem: Currently we do not save the output from the docker daemon anywhere, let's redirect it to /var/log/docker. Every next run will append to the file. A patch attached, created against master. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang November 2013