Bug 1464790 - Docker containers cannot connect to the internet
Summary: Docker containers cannot connect to the internet
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: docker
Version: 24
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Antonio Murdaca
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1464791 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-25 19:46 UTC by Mebus
Modified: 2017-07-10 21:04 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-06-27 11:47:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Mebus 2017-06-25 19:46:24 UTC
Description of problem:

Docker Containers in Fedora 24 cannot connect to the internet, when firewalld is used.

This:

https://opsech.io/posts/2017/May/23/docker-dns-with-firewalld-on-fedora.html

fixed the DNS issue, but I still cannot connect to the internet from within a container.

Comment 1 Daniel Walsh 2017-06-26 13:25:34 UTC
*** Bug 1464791 has been marked as a duplicate of this bug. ***

Comment 2 Antonio Murdaca 2017-06-27 10:06:14 UTC
which docker version are you using? Could you also add steps to reproduce? A bugzilla filed like this isn't helping people trying to fix the bug.

Comment 3 Antonio Murdaca 2017-06-27 10:12:17 UTC
from what I can see, on Fedora 24 you're still using docker-1.10.x. I'm probably going to fix this in 1.12.x however, could you try and use docker-latest instead (which is at 1.12.x)?

Comment 4 Antonio Murdaca 2017-06-27 10:28:57 UTC
This is a risky backport for docker 1.10.x - I've backported the patch to the 1.12.x branch:

https://github.com/projectatomic/docker/commit/e07b00065849faf8b811090476f8d9cccebbd59f

That will be soon available as "docker-latest" in Fedora 24. I want to point out that F24 will be EOL'ed in around a month so either use docker-latest there, or upgrade your Fedora.

Comment 5 Daniel Walsh 2017-06-27 11:47:55 UTC
Yes lets close this as fixed in the next release.

Comment 6 Mebus 2017-07-10 21:04:43 UTC
It was a network problem (TTL).

Mebus


Note You need to log in before you can comment on or make changes to this bug.