golang March 2014

golang@lists.fedoraproject.org

6 participants
126 discussions

[Bug 1045173] New: Accessing Docker containers from outside network - adding firewall exceptions problem
by Red Hat Bugzilla 28 May '14

28 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1045173 Bug ID: 1045173 Summary: Accessing Docker containers from outside network - adding firewall exceptions problem Product: Fedora EPEL Version: el6 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: ajinkya(a)ajinkyakulkarni.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, skottler(a)redhat.com, vbatts(a)redhat.com I am using Docker 0.7.0 to create containers on RedHat Enterprise Linux 6.5. When firewall is turned off containers can talk to outside world, but when firewall is on, container cannot be accessed from outside. This is how I am running the docker and mapping a port from host to container $ docker run -i -t -p 3838:3838 shiny "shiny-server" Without firewall, I can access Node.js server running inside a container on port 3838 from outside network as http://servername:3838, but not with firewall turned on. These are my default firewall rules – ============================================== # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT -A INPUT -j REJECT --reject-with icmp-host-prohibited -A FORWARD -j REJECT --reject-with icmp-host-prohibited COMMIT ============================================== I have tried opening a port 3838 by adding a rule as below, but it does not work -A INPUT -m state --state NEW -m tcp -p tcp --dport 3838 -j ACCEPT Docker is creating a virtual NAT on the host machine, I am feeling that somehow firewall is blocking the packet forwarding from eth0 to docker 0 This is the output of $ifconfig (I have masked the server IP) docker0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:172.17.42.1 Bcast:0.0.0.0 Mask:255.255.0.0 inet6 addr: fe80::87d:8dff:fed0:f16d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:408321 errors:0 dropped:0 overruns:0 frame:0 TX packets:681809 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:126511933 (120.6 MiB) TX bytes:924200959 (881.3 MiB) eth0 Link encap:Ethernet HWaddr 00:25:64:A8:5B:8F inet addr:XXX.XXX.XXX.XXX Bcast:XXX.XXX.XXX.XXX Mask:255.255.240.0 inet6 addr: XXXX::XXX:XXXX:XXXX:XXXX/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:29786186 errors:0 dropped:0 overruns:0 frame:0 TX packets:1137982 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4209047011 (3.9 GiB) TX bytes:234657696 (223.7 MiB) Interrupt:17 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:8444 errors:0 dropped:0 overruns:0 frame:0 TX packets:8444 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4701771 (4.4 MiB) TX bytes:4701771 (4.4 MiB) Output of $docker version : Client version: 0.7.0 Go version (client): go1.1.2 Git commit (client): 0ff9bc1/0.7.0 Server version: 0.7.0 Git commit (server): 0ff9bc1/0.7.0 Go version (server): go1.1.2 Last stable version: 0.7.2, please update docker Output of $docker info: Containers: 321 Images: 278 Driver: devicemapper Pool Name: docker-8:17-13239310-pool Data file: /var/lib/docker/devicemapper/devicemapper/data Metadata file: /var/lib/docker/devicemapper/devicemapper/metadata Data Space Used: 56464.5 Mb Data Space Total: 102400.0 Mb Metadata Space Used: 59.5 Mb Metadata Space Total: 2048.0 Mb I need help in making docker containers accessible from outside network without turning off the entire firewall. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1071896] New: Fedora base image update failure in trusted builds at Docker index
by Red Hat Bugzilla 28 May '14

28 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1071896 Bug ID: 1071896 Summary: Fedora base image update failure in trusted builds at Docker index Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: nshaikh(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org 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 Description of problem: I am using trusted build feature of Docker index and using Dockerfile [1] to build an image at Docker index. Dockerfile[1] is using stackbrew/fedora as base image. I am running "yum -y update" command in Dockerfile, however update is failing for systemd.x86_64 0:208-9.fc20 , check logs here[2]. I have retried building the image at Docker index, however each time it is failing with same error. Logs for 4 builds:[3] [1] https://github.com/swordphilic/redis-fedora/blob/master/Dockerfile [2] https://index.docker.io/builds/github/2159/swordphilic/redis-fedora/builds/… [3] https://index.docker.io/builds/github/2159/swordphilic/redis-fedora/builds -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1041400] New: docker permission denied errors
by Red Hat Bugzilla 22 May '14

22 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1041400 Bug ID: 1041400 Summary: docker permission denied errors Product: Fedora Version: rawhide Component: docker-io 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, mgoldman(a)redhat.com, vbatts(a)redhat.com Description of problem: rest api calls seem to fail for docker on rawhide Version-Release number of selected component (if applicable): 0.7.1 (both rpm and binary released by upstream) How reproducible: consistent Steps to Reproduce: 1. install docker-io (via yum or upstream binary) 2. try 'docker search' / 'docker pull' / 'docker login' or anything else Actual results: $ sudo docker search fedora 2013/12/12 09:43:53 Error: Get https://index.docker.io/v1/search?q=fedora: dial tcp 54.234.135.251:443: permission denied Expected results: should show a list of fedora images Additional info: I didn't find this in f19 or epel (only on rawhide) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1057340] New: rpm macros for golang
by Red Hat Bugzilla 21 May '14

21 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1057340 Bug ID: 1057340 Summary: rpm macros for golang 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, skottler(a)redhat.com, vbatts(a)redhat.com include in the golang rpm an /etc/rpm/macros.golang for defining %gopath such that it is a system definition. There may be other rpm automations to add as well. Ideally a post script for __spec_install_post that could produce Provides: and Requires: of the golang() libraries exported and imported. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 1071605] New: sshd not working in fedora image
by Red Hat Bugzilla 15 May '14

15 May '14

https://bugzilla.redhat.com/show_bug.cgi?id=1071605 Bug ID: 1071605 Summary: sshd not working in fedora image Product: Fedora Version: 20 Component: docker-io Assignee: lsm5(a)redhat.com Reporter: pantinor(a)redhat.com QA Contact: extras-qa(a)fedoraproject.org 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 Description of problem: Running sshd on a fresh docker fedora image fails with this error: Failed to get D-Bus connection: No connection to service manager. Version-Release number of selected component (if applicable): $ docker -v Docker version 0.8.0, build cc3a8c8/0.8.0 $ docker inspect fedora [{ "id": "58394af373423902a1b97f209a31e3777932d9321ef10e64feaaa7b4df609cf9", "parent": "8abc22fbb04266308ff408ca61cb8f6f4244a59308f7efc64e54b08b496c58db", "created": "2014-02-03T16:10:40.500814677Z", "container": "f718f19a28a5147da49313c54620306243734bafa63c76942ef6f8c4b4113bc5", "container_config": { "Hostname": "88807319f25e", "Domainname": "", "User": "", "Memory": 0, "MemorySwap": 0, "CpuShares": 0, "AttachStdin": false, "AttachStdout": false, "AttachStderr": false, "PortSpecs": null, "ExposedPorts": null, "Tty": false, "OpenStdin": false, "StdinOnce": false, "Env": [ "HOME=/", "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" ], "Cmd": [ "/bin/sh", "-c", "#(nop) ADD fedora-20-medium.tar.xz in /" ], "Dns": null, "Image": "8abc22fbb04266308ff408ca61cb8f6f4244a59308f7efc64e54b08b496c58db", "Volumes": null, "VolumesFrom": "", "WorkingDir": "", "Entrypoint": null, "NetworkDisabled": false, "OnBuild": null }, "docker_version": "0.6.3", "author": "Lokesh Mandvekar \u003clsm5(a)redhat.com\u003e - ./buildcontainers.sh", "config": { "Hostname": "88807319f25e", "Domainname": "", "User": "", "Memory": 0, "MemorySwap": 0, "CpuShares": 0, "AttachStdin": false, "AttachStdout": false, "AttachStderr": false, "PortSpecs": null, "ExposedPorts": null, "Tty": false, "OpenStdin": false, "StdinOnce": false, "Env": [ "HOME=/", "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" ], "Cmd": null, "Dns": null, "Image": "8abc22fbb04266308ff408ca61cb8f6f4244a59308f7efc64e54b08b496c58db", "Volumes": null, "VolumesFrom": "", "WorkingDir": "", "Entrypoint": null, "NetworkDisabled": false, "OnBuild": null }, "architecture": "x86_64", "Size": 385520098 }] How reproducible: Always Steps to Reproduce: 1. docker run -t -i fedora bash 2. bash-4.2# yum install -y openssh-server 3. bash-4.2# systemctl start sshd Actual results: Failed to get D-Bus connection: No connection to service manager. bash-4.2# service sshd status Redirecting to /bin/systemctl status sshd.service Failed to get D-Bus connection: No connection to service manager. Expected results: A running sshd daemon Additional info: -- You are receiving this mail because: You are on the CC list for the bug.

1 4

Broken dependencies: golang-github-guelfey-godbus
by Fedora Koji Build System 31 Mar '14

31 Mar '14

golang-github-guelfey-godbus has broken dependencies in the epel-7 tree: On ppc64: golang-github-guelfey-godbus-devel-0-0.1.gitf6a3a23.el7.noarch requires golang Please resolve this as soon as possible.

1 0

Broken dependencies: golang-github-smarterclayton-go-systemd
by Fedora Koji Build System 31 Mar '14

31 Mar '14

golang-github-smarterclayton-go-systemd has broken dependencies in the epel-7 tree: On ppc64: golang-github-smarterclayton-go-systemd-devel-0-0.4.git5cb9e9e.el7.noarch requires golang Please resolve this as soon as possible.

1 0

Broken dependencies: golang-github-smarterclayton-go-systemd
by Fedora Koji Build System 30 Mar '14

30 Mar '14

1 0

Broken dependencies: golang-github-guelfey-godbus
by Fedora Koji Build System 30 Mar '14

30 Mar '14

1 0

[Bug 1080498] Review Request: golang-github-smarterclayton-go-systemd - Go bindings to systemd D-BUS APIs
by Red Hat Bugzilla 29 Mar '14

29 Mar '14

https://bugzilla.redhat.com/show_bug.cgi?id=1080498 Fedora Update System <updates(a)fedoraproject.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|MODIFIED |ON_QA --- Comment #11 from Fedora Update System <updates(a)fedoraproject.org> --- golang-github-smarterclayton-go-systemd-0-0.4.git5cb9e9e.el6 has been pushed to the Fedora EPEL 6 testing repository. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

golang March 2014