November 2013 - golang - Fedora Mailing-Lists

[Bug 1034919] New: Docker-io needs libcgroup installed and running in order to function

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1034919 Bug ID: 1034919 Summary: Docker-io needs libcgroup installed and running in order to function Product: Fedora EPEL Version: el6 Component: docker-io Severity: high Assignee: lsm5(a)redhat.com Reporter: nux(a)li.nux.ro 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: "docker run" will error out when cgroups are not present: "[error] commands.go:2459 Error resize: Error: bad file descriptor" Version-Release number of selected component (if applicable): 0.7 0.20.rc7.el6 How reproducible: always Steps to Reproduce: 1. yum --enablerepo=epel-testing install docker-io 2. service docker start 3. docker run -i -t ubuntu /bin/bash Actual results: "[error] commands.go:2459 Error resize: Error: bad file descriptor" Expected results: BASH prompt in the container Additional info: Installing cgroups fixes the problem: "yum -y install libcgroup && service cgconfig start" -- You are receiving this mail because: You are on the CC list for the bug.

10 years, 4 months

1
22
0 / 0

[ANN] RHEL EPEL and Fedora package maintainer

by Vincent Batts

Hello all, I wanted to make a quick introduction since it does not look to have happened yet. Between Adam Goode, Adam Miller, and myself, we maintain the golang compiler package for recent versions of Fedora and EPEL for RHEL6 [1]. There is a mailing list for community related conversation about golang as well [2]. So "hello", and feel free to ping us or reach out. Take care, vb [1] http://koji.fedoraproject.org/koji/packageinfo?packageID=16224 [2] https://lists.fedoraproject.org/mailman/listinfo/golang

10 years, 4 months

3
3
0 / 0

[Bug 1035436] New: support for bridge networking

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1035436 Bug ID: 1035436 Summary: support for bridge networking Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)redhat.com Reporter: vbatts(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: docker reports that bridge networking on RHEL, even when bridge-utils is installed. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. docker -d 2. 3. Actual results: # docker -d 2013/11/27 13:40:18 WARNING: You are running linux kernel version 2.6.32-358.23.2.el6.x86_64, which might be unstable running docker. Please upgrade your kernel to 3.8.0. [/var/lib/docker|1bff374f] +job initapi() [/var/lib/docker|1bff374f.initapi()] Creating server [/var/lib/docker|1bff374f] -job initapi() = ERR (Error creating bridge: operation not supported) 2013/11/27 13:40:18 initapi: Error creating bridge: operation not supported Expected results: 2013/11/27 13:41:37 WARNING: You are running linux kernel version 2.6.32-358.23.2.el6.x86_64, which might be unstable running docker. Please upgrade your kernel to 3.8.0. [/var/lib/docker|30c81777] +job initapi() [/var/lib/docker|30c81777.initapi()] Creating server Loading containers: -[error] runtime.go:271 Failed to load container 844a5f802d474b7ec5de5c4ef4678ac3c478bc879ce3a79a5359fa9e760d5716: open /var/lib/docker/containers/844a5f802d474b7ec5de5c4ef4678ac3c478bc879ce3a79a5359fa9e760d5716/config.json: no such file or directory done. [/var/lib/docker|30c81777.initapi()] Creating pidfile [/var/lib/docker|30c81777.initapi()] Setting up signal traps [/var/lib/docker|30c81777] Register(create) (handlers=map[initapi:0x4911e0]) [/var/lib/docker|30c81777] Register(start) (handlers=map[initapi:0x4911e0 create:0x4aec50]) [/var/lib/docker|30c81777] Register(serveapi) (handlers=map[initapi:0x4911e0 create:0x4aec50 start:0x4aecb0]) [/var/lib/docker|30c81777] -job initapi() = OK (0) [/var/lib/docker|30c81777] +job serveapi(unix:///var/run/docker.sock) 2013/11/27 13:41:37 Listening for HTTP on /var/run/docker.sock (unix) Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

10 years, 4 months

1
3
0 / 0

[Bug 1032094] New: `docker -d -b=none` fails with a nil pointer

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1032094 Bug ID: 1032094 Summary: `docker -d -b=none` fails with a nil pointer Product: Fedora Version: rawhide Component: docker-io Assignee: lsm5(a)redhat.com Reporter: vbatts(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: https://github.com/dotcloud/docker/issues/2768 Version-Release number of selected component (if applicable): Docker version 0.7, build 457375e/0.14.rc5.el6 How reproducible: consistent Steps to Reproduce: 1. docker -d -b=none 2. 3. Actual results: http://pastebin.com/6PJb8LZ6 Expected results: The docker daemon to run Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

10 years, 4 months

1
4
0 / 0

[Bug 1026976] New: "Error starting container, Error adding device, can't find device for parent ''" when starting fedora docker image

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1026976 Bug ID: 1026976 Summary: "Error starting container, Error adding device, can't find device for parent ''" when starting fedora docker image 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: Running container fails with: Error: Error starting container 43e36bc82ecd: Error adding device for '0f3e92b4e94d643339d14b096ade73b42b28ff6f9be99064696a97f248c1a651': can't find device for parent '' Additionally /var/log/messages has this: Nov 5 10:20:20 docker kernel: [ 85.389079] device-mapper: space map common: index_check failed: blocknr 0 != wanted 314 Nov 5 10:20:20 docker kernel: [ 85.389102] device-mapper: block manager: index validator check failed for block 314 Nov 5 10:20:20 docker kernel: [ 85.389284] device-mapper: transaction manager: couldn't open metadata space map Nov 5 10:20:20 docker kernel: [ 85.389295] device-mapper: thin metadata: tm_open_with_sm failed Nov 5 10:20:20 docker kernel: [ 85.390964] device-mapper: table: 253:1: thin-pool: Error creating metadata object Nov 5 10:20:20 docker kernel: [ 85.391095] device-mapper: ioctl: error adding target to table Version-Release number of selected component (if applicable): # rpm -qa docker-io docker-io-0.7-0.13.dm.fc19.x86_64 # uname -a Linux ... 3.11.6-200.fc19.x86_64 #1 SMP Fri Oct 18 22:34:18 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux How reproducible: Every time Steps to Reproduce: 1. Install docker-io-0.7-0.13.dm.fc19.x86_64.rpm 2. Start docker daemon (docker -d &) 3. Download mattdm/fedora images (docker pull mattdm/fedora) 4. Try to start a fedora image (docker run -i -t mattdm/fedora /bin/bash) Actual results: Error: Error starting container 96c6d2706331: Error adding device for '0f3e92b4e94d643339d14b096ade73b42b28ff6f9be99064696a97f248c1a651': can't find device for parent '' Expected results: Shell access to fedora container Additional info: My rootfs is on an LV fedora-root in VG fedora # dmsetup ls --tree fedora-root (253:0) └─ (252:2) Not sure if that would make a difference. -- You are receiving this mail because: You are on the CC list for the bug.

10 years, 4 months

1
4
0 / 0

[Bug 1035307] New: Add README.fedora with information on how to start using the package

by Red Hat Bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1035307 Bug ID: 1035307 Summary: Add README.fedora with information on how to start using the package 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: Currently the docker0 bridge cannot be created automatically, we need to add instructions on how to do it manually so containers can have network connectivity. -- You are receiving this mail because: You are on the CC list for the bug.

10 years, 4 months

1
2
0 / 0

[docker-io/el6: 2/2] Merge branch 'master' into el6

by Lokesh Mandvekar

commit c275b773820e73b7517d71eb3dd594718941a994 Merge: 5a35ce7 ab27c4d Author: Lokesh Mandvekar <lsm5(a)redhat.com> Date: Thu Nov 28 12:37:06 2013 -0600 Merge branch 'master' into el6 80-docker.rules | 2 ++ docker-io.spec | 20 +++++++++++++++++--- 2 files changed, 19 insertions(+), 3 deletions(-) ---

10 years, 5 months

1
0
0 / 0

[docker-io/el6] (2 commits) ...Merge branch 'master' into el6

by Lokesh Mandvekar

Summary of changes: ab27c4d... udev rules added BZ 1034095 (*) c275b77... Merge branch 'master' into el6 (*) This commit already existed in another branch; no separate mail sent

10 years, 5 months

1
0
0 / 0

[docker-io/f19] udev rules added BZ 1034095

by Lokesh Mandvekar

Summary of changes: ab27c4d... udev rules added BZ 1034095 (*) (*) This commit already existed in another branch; no separate mail sent

10 years, 5 months

1
0
0 / 0

[docker-io/f20: 2/2] Merge branch 'master' into f20

by Lokesh Mandvekar

commit 44d1cd0f6d53d84b9ea9633d3156e2e78e2c6176 Merge: 8f7798e ab27c4d Author: Lokesh Mandvekar <lsm5(a)redhat.com> Date: Thu Nov 28 12:17:30 2013 -0600 Merge branch 'master' into f20 80-docker.rules | 2 ++ docker-io.spec | 20 +++++++++++++++++--- 2 files changed, 19 insertions(+), 3 deletions(-) ---

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang November 2013