Use docker 1.12.5

Docker uses an embedded DNS server (127.0.0.11) for user defined networks (UDN).

With the latest releases of docker, specifying 127.0.0.1 as --dns makes the
containers resolve 127.0.0.1 _inside_ the container's networking namespace
(not sure how it worked before this).

The next idea was to only specify --dns-search=. but this does not work.
This makes docker setup the containers to use 127.0.0.1 (or 127.0.0.11 for UDN).
In my mind, the UDN case should work but doesn't (not sure why).

So, the solution is to simply go with no --dns or --dns-search. Sadly,
setting dns-search just at container level does not work either :/ Strangely,

    docker run --network=cloudron --dns-search=. appimage  # does not work

    docker run --network=cloudron appimage # works if you manually remove search from /etc/resolv.conf

So clearly, something inside docker triggers when one of the dns* options is set.

This means that #130 has to be fixed at app level (For Go, this means to use the cgo resolver).

This commit is contained in:

Girish Ramakrishnan

2016-12-23 10:07:06 -08:00

parent f5eb5d545f

commit 691f6c7c5c

3 changed files with 9 additions and 37 deletions

									
										src/infra_version.js
									
		+1
		-1
	
												View File
												
				@@ -6,7 +6,7 @@

				exports = module.exports = {

				    // a version bump means that all containers (apps and addons) are recreated

				    'version': 42,

				    'version': 43,

				    'baseImages': [ 'cloudron/base:0.9.0' ],