[Bug 1034951] golang-vim has unsatisfied dependencies on epel6
https://bugzilla.redhat.com/show_bug.cgi?id=1034951 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #6 from Fedora Update System --- Package golang-1.1.2-8.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing golang-1.1.2-8.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-5/golang-1.1.2-8.fc19 then log in and leave karma (feedback). -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #15 from Josh Poimboeuf --- > > The debug trace you posted seemed to show that docker0 already existed. So > > what I'm still confused about is how is the the docker0 device getting > > created to start with? It looks like somebody created docker0 without > > setting up its needed iptables rules. > > I wouldn't assume this, since the rules are executed no matter if the > docker0 interface is started up or not: > > https://github.com/dotcloud/docker/blob/v0.7.0/iptables/iptables.go#L105 > > This bridge was created by running the systemd service, no other tool > created it. Actually the rules that seem to be missing are the ones in the FORWARD table, which are created whenever the docker0 bridge is created: https://github.com/dotcloud/docker/blob/v0.7.0/network.go#L180 -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1034095] Hide devicemapper mounts in Gnome
https://bugzilla.redhat.com/show_bug.cgi?id=1034095 Andy Lutomirski changed: What|Removed |Added CC||l...@mit.edu --- Comment #3 from Andy Lutomirski --- What's needed is (I think) UDISKS_IGNORE [1] [2]. [1] https://git.gnome.org/browse/gvfs/tree/monitor/udisks2/what-is-shown.txt [2] udisks.8 This may be as simple as having a standard naming convention for Docker's DM devices and adding a udev rule. -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1034951] golang-vim has unsatisfied dependencies on epel6
https://bugzilla.redhat.com/show_bug.cgi?id=1034951 --- Comment #5 from Vincent Batts --- updated package pushed to bodhi https://admin.fedoraproject.org/updates/golang-1.1.2-8.el6?_csrf_token=136afe32863db9262ace7bec0c00a0704c09b4b6 -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1034951] golang-vim has unsatisfied dependencies on epel6
https://bugzilla.redhat.com/show_bug.cgi?id=1034951 --- Comment #4 from Fedora Update System --- golang-1.1.2-8.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/golang-1.1.2-8.fc20 -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1034951] golang-vim has unsatisfied dependencies on epel6
https://bugzilla.redhat.com/show_bug.cgi?id=1034951 --- Comment #3 from Fedora Update System --- golang-1.1.2-8.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/golang-1.1.2-8.fc19 -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1034951] golang-vim has unsatisfied dependencies on epel6
https://bugzilla.redhat.com/show_bug.cgi?id=1034951 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1034951] golang-vim has unsatisfied dependencies on epel6
https://bugzilla.redhat.com/show_bug.cgi?id=1034951 --- Comment #2 from Fedora Update System --- golang-1.1.2-8.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/golang-1.1.2-8.el6 -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1034951] golang-vim has unsatisfied dependencies on epel6
https://bugzilla.redhat.com/show_bug.cgi?id=1034951 --- Comment #1 from Vincent Batts --- http://koji.fedoraproject.org/koji/taskinfo?taskID=6229216 I'll push this update out once it's passed all the checks. -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1034951] golang-vim has unsatisfied dependencies on epel6
https://bugzilla.redhat.com/show_bug.cgi?id=1034951 Vincent Batts changed: What|Removed |Added Status|NEW |ASSIGNED CC||vba...@redhat.com Assignee|admil...@redhat.com |vba...@redhat.com -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1034951] New: golang-vim has unsatisfied dependencies on epel6
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: admil...@redhat.com Reporter: t...@foobar.fi QA Contact: extras...@fedoraproject.org CC: a...@spicenitz.org, admil...@redhat.com, golang@lists.fedoraproject.org, l...@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. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1034919] Docker-io needs libcgroup installed and running in order to function
https://bugzilla.redhat.com/show_bug.cgi?id=1034919 Vincent Batts changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|l...@redhat.com |vba...@redhat.com -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1034919] New: Docker-io needs libcgroup installed and running in order to function
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: l...@redhat.com Reporter: n...@li.nux.ro QA Contact: extras...@fedoraproject.org CC: golang@lists.fedoraproject.org, l...@redhat.com, mat...@redhat.com, vba...@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. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #14 from Marek Goldmann --- (In reply to Josh Poimboeuf from comment #13) > Sorry, I misunderstood. It should be ok for docker to leave the docker0 > bridge device after it exits. In fact it's probably necessary so that > already running containers won't lose their network if the docker daemon has > to restart. > > When docker starts up, it checks for the existence of docker0. If it > doesn't exist then it creates it and sets up the iptables rules > appropriately. So future starts of docker will re-use the same bridge > device, which should work fine. OK, this makes sense. > The debug trace you posted seemed to show that docker0 already existed. So > what I'm still confused about is how is the the docker0 device getting > created to start with? It looks like somebody created docker0 without > setting up its needed iptables rules. I wouldn't assume this, since the rules are executed no matter if the docker0 interface is started up or not: https://github.com/dotcloud/docker/blob/v0.7.0/iptables/iptables.go#L105 This bridge was created by running the systemd service, no other tool created it. -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #13 from Josh Poimboeuf --- > Josh, above are devices. These cannot be listed with the "systemctl > list-unit-files" command. I think the real issue is that docker leaves the > docker0 interface running, even after we stop the service. WDYT? Sorry, I misunderstood. It should be ok for docker to leave the docker0 bridge device after it exits. In fact it's probably necessary so that already running containers won't lose their network if the docker daemon has to restart. When docker starts up, it checks for the existence of docker0. If it doesn't exist then it creates it and sets up the iptables rules appropriately. So future starts of docker will re-use the same bridge device, which should work fine. The debug trace you posted seemed to show that docker0 already existed. So what I'm still confused about is how is the the docker0 device getting created to start with? It looks like somebody created docker0 without setting up its needed iptables rules. -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #12 from Marek Goldmann --- (In reply to Josh Poimboeuf from comment #11) > Ok. Removing those unit files and rebooting should fix the issue. Josh, above are devices. These cannot be listed with the "systemctl list-unit-files" command. I think the real issue is that docker leaves the docker0 interface running, even after we stop the service. WDYT? -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #11 from Josh Poimboeuf --- Ok. Removing those unit files and rebooting should fix the issue. -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #10 from Marek Goldmann --- (In reply to Josh Poimboeuf from comment #9) > There should be more docker-related rules there. Is there a unit file that > creates the docker0 device before docker starts? If so, remove it so that > docker can create it and set up its iptables rules. This is what I have: $ systemctl list-units -a | grep docker sys-devices-virtual-net-docker0.device loadedactive plugged /sys/devices/virtual/net/docker0 sys-subsystem-net-devices-docker0.device loadedactive plugged /sys/subsystem/net/devices/docker0 docker.service loadedinactive dead Docker container management daemon And indeed, the docker0 interface is up, even when we stop the docker service. -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #9 from Josh Poimboeuf --- This isn't right: Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- docker0 docker0 anywhere anywhere There should be more docker-related rules there. Is there a unit file that creates the docker0 device before docker starts? If so, remove it so that docker can create it and set up its iptables rules. -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #8 from Michal Fojtik --- Marek: http://fpaste.org/56877/38547748/ -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #7 from Michal Fojtik --- FYI I was playing with this and I discover this (dunno if it helps): [root@localhost redis-server]# docker run -i -t mattdm/fedora /bin/bash bash-4.2# ping google.com ping: unknown host google.com [root@localhost redis-server]# systemctl stop firewalld [root@localhost redis-server]# docker run -i -t mattdm/fedora /bin/bash lxc-start: failed to attach 'vethkb9kR0' to the bridge 'docker0' : No such device lxc-start: failed to create netdev lxc-start: failed to create the network lxc-start: failed to spawn '1db793c53b22a2fda433a9ce2ddbb9022cca6a0c33126389ac95ca7b176c947c' [error] commands.go:2459 Error resize: Error: bad file descriptor [root@localhost redis-server]# systemctl restart docker [root@localhost redis-server]# docker run -i -t mattdm/fedora /bin/bash bash-4.2# ping google.com PING google.com (173.194.41.135) 56(84) bytes of data. -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #6 from Marek Goldmann --- After boot I cannot connect to the Internet from container, but when I do: systemctl restart firewalld systemctl restart docker then I can. Restarting docker service alone does not help. Adding hard requires to docker systemd file in the [Unit] section: Requires=firewalld.service doesn't help either. BTW, we should add "Wants=firewalld.service" to make sure the firewalld service is started before Docker, if it's available. I suspect that the issue is in the time which is needed to create all the required devices. If we add: ExecStartPre=/usr/bin/sleep 3 to the [Service] section makes it possible to connect to the Internet from the container. Even 1s is sufficient on my system. -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #5 from Marek Goldmann --- We have following rules executed: The systemd service (before docker starts): /usr/sbin/sysctl -w net.ipv4.ip_forward=1 net.ipv6.conf.all.forwarding=1 And docker runs this on its own: lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-D FORWARD -i docker0 -o docker0 -j DROP] lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-C FORWARD -i docker0 -o docker0 -j ACCEPT] lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-t nat -D PREROUTING -m addrtype --dst-type LOCAL -j DOCKER] lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-t nat -D OUTPUT -m addrtype --dst-type LOCAL ! --dst 127.0.0.0/8 -j DOCKER] lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-t nat -D OUTPUT -m addrtype --dst-type LOCAL -j DOCKER] lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-t nat -D PREROUTING -j DOCKER] lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-t nat -D OUTPUT -j DOCKER] lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-t nat -F DOCKER] lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-t nat -X DOCKER] lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-t nat -N DOCKER] lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-t nat -A PREROUTING -m addrtype --dst-type LOCAL -j DOCKER] lis 26 10:43:15 mistress docker[11602]: [DEBUG] [iptables]: /usr/sbin/iptables, [-t nat -A OUTPUT -m addrtype --dst-type LOCAL ! --dst 127.0.0.0/8 -j DOCKER] -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
[docker-io] Upstream release 0.7.0
commit 2b4214c22ecc24d0fc6f24c653f0c34b88fcd863
Author: Marek Goldmann
Date: Tue Nov 26 09:54:44 2013 +0100
Upstream release 0.7.0
.gitignore |1 +
docker-bridge_flag.patch | 16
docker-io.spec | 41 ++---
sources |2 +-
4 files changed, 20 insertions(+), 40 deletions(-)
---
diff --git a/.gitignore b/.gitignore
index e646e94..11eea8b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -7,3 +7,4 @@
/docker-268e386.tar.gz
/docker-9af7730.tar.gz
/docker-ea7811c.tar.gz
+/v0.7.0.tar.gz
diff --git a/docker-io.spec b/docker-io.spec
index eaaec20..48a9670 100644
--- a/docker-io.spec
+++ b/docker-io.spec
@@ -9,22 +9,21 @@
%global debug_package %{nil}
%global gopath %{_datadir}/gocode
-%global commit ea7811c83d913db91948cd4f696cf34b139da855
+%global commit 0d078b65817fc91eba916652b3f087a6c2eef851
%global shortcommit %(c=%{commit}; echo ${c:0:7})
Name: docker-io
-Version:0.7
-Release:0.20.rc7%{?dist}
+Version:0.7.0
+Release:1%{?dist}
Summary:Automates deployment of containerized applications
License:ASL 2.0
Patch0: docker-0.7-remove-dotcloud-tar.patch
Patch1: docker-0.7-el6-docs.patch
-Patch2: docker-bridge_flag.patch
URL:http://www.docker.io
# only x86_64 for now: https://github.com/dotcloud/docker/issues/136
ExclusiveArch: x86_64
-Source0:
https://github.com/crosbymichael/docker/archive/%{commit}/docker-%{shortcommit}.tar.gz
+Source0:https://github.com/dotcloud/docker/archive/v%{version}.tar.gz
Source1:docker.service
# though final name for sysconf/sysvinit files is simply 'docker',
# having .sysvinit and .sysconfig makes things clear
@@ -60,33 +59,25 @@ and tests on a laptop will run at scale, in production*, on
VMs, bare-metal
servers, OpenStack clusters, public instances, or combinations of the above.
%prep
-%setup -q -n docker-%{commit}
+%setup -q -n docker-%{version}
rm -rf vendor
%patch0 -p1 -b docker-0.7-remove-dotcloud-tar.patch
%if 0%{?rhel} >= 6
%patch1 -p1 -b docker-0.7-el6-docs.patch
%endif
-%patch2 -p1 -b none-bridge
%build
mkdir _build
+
pushd _build
+ mkdir -p src/github.com/dotcloud
+ ln -s $(dirs +1 -l) src/github.com/dotcloud/docker
+popd
-mkdir -p src/github.com/dotcloud
-ln -s $(dirs +1 -l) src/github.com/dotcloud/docker
-export GOPATH=$(pwd):%{gopath}
-# passing version information build flags BZ #1017186
-export LDFLAGS="-X main.GITCOMMIT '%{shortcommit}/%{release}' -X main.VERSION
'%{version}' -w"
-export LDFLAGS_STATIC="-X github.com/dotcloud/docker/utils.IAMSTATIC true"
-export BUILDFLAGS="-tags netgo"
-go build -v -a -ldflags \
- "$LDFLAGS -linkmode external -extldflags '-lpthread -static
-Wl,--unresolved-symbols=ignore-in-object-files' $LDFLAGS_STATIC" \
- $BUILDFLAGS \
- github.com/dotcloud/docker/dockerinit
-export DOCKER_INITSHA1="$(sha1sum dockerinit | cut -d' ' -f1)"
-go build -v -a -ldflags "$LDFLAGS -X github.com/dotcloud/docker/utils.INITSHA1
\"$DOCKER_INITSHA1\"" $BUILDFLAGS github.com/dotcloud/docker/docker
+export DOCKER_GITCOMMIT="%{shortcommit}/%{version}"
+export GOPATH=$(pwd)/_build:%{gopath}
-popd
+hack/make.sh dynbinary
make -C docs/ man
@@ -97,8 +88,8 @@ install -d %{buildroot}%{_mandir}/man1
install -d %{buildroot}%{_sysconfdir}/bash_completion.d
install -d %{buildroot}%{_datadir}/zsh/site-functions
install -d -m 700 %{buildroot}%{_sharedstatedir}/docker
-install -p -m 755 _build/docker %{buildroot}%{_bindir}/docker
-install -p -m 755 _build/dockerinit %{buildroot}%{_libexecdir}/docker
+install -p -m 755 bundles/%{version}/dynbinary/docker-%{version}
%{buildroot}%{_bindir}/docker
+install -p -m 755 bundles/%{version}/dynbinary/dockerinit-%{version}
%{buildroot}%{_libexecdir}/docker/dockerinit
install -p -m 644 docs/_build/man/docker.1 %{buildroot}%{_mandir}/man1
install -p -m 644 contrib/completion/bash/docker
%{buildroot}%{_sysconfdir}/bash_completion.d/docker.bash
install -p -m 644 contrib/completion/zsh/_docker
%{buildroot}%{_datadir}/zsh/site-functions
@@ -156,6 +147,10 @@ exit 0
%dir %{_sharedstatedir}/docker
%changelog
+* Tue Nov 26 2013 Marek Goldmann - 0.7.0-1
+- Upstream release 0.7.0
+- Using upstream script to build the binary
+
* Mon Nov 25 2013 Vincent Batts - 0.7-0.20.rc7
- correct the build time defines (bz#1026545). Thanks dan-fedora.
diff --git a/sources b/sources
index 0e4ebfa..b0fdf17 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-852051f88f023aa84db32e98751f834a docker-ea7811c.tar.gz
+bc5e2aa1fbcd3ab8fac1a4f6a4613a16 v0.7.0.tar.gz
___
golang mailing list
golang@lists.fedoraproject.org
https://lists.fedoraproject.org/mailman/listinfo/golang
[Bug 1033606] Failed to connect to network from Docker container
https://bugzilla.redhat.com/show_bug.cgi?id=1033606 --- Comment #4 from Marek Goldmann --- Created attachment 829120 --> https://bugzilla.redhat.com/attachment.cgi?id=829120&action=edit iptables output I can see this issue as well, with the upcoming 0.7.0-1 release, attaching my iptables output. -- You are receiving this mail because: You are on the CC list for the bug. ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
File v0.7.0.tar.gz uploaded to lookaside cache by goldmann
A file has been added to the lookaside cache for docker-io: bc5e2aa1fbcd3ab8fac1a4f6a4613a16 v0.7.0.tar.gz ___ golang mailing list golang@lists.fedoraproject.org https://lists.fedoraproject.org/mailman/listinfo/golang
