Closed horkhe closed 8 years ago
this is a dupe of #542 and referenced to be fixed in #557
I'm not seeing any host related things on the resource in the stack trace... this is probably a real bug
can you paste the output of "docker info" ?
@someara I dealt with this in the past and going off of memory here, this is an issue with docker 1.9.0.
I think it is because we pass 'Hostname' => hostname
to the docker create, prior to 1.9.0 docker would ignore it because it is nil. Now docker will actually complain about it because we are passing it during the create method.
@someara here you are:
$ docker info
Containers: 2
Images: 51
Server Version: 1.9.1
Storage Driver: devicemapper
Pool Name: docker-8:1-530890-pool
Pool Blocksize: 65.54 kB
Base Device Size: 107.4 GB
Backing Filesystem:
Data file: /dev/loop0
Metadata file: /dev/loop1
Data Space Used: 2.925 GB
Data Space Total: 107.4 GB
Data Space Available: 26.47 GB
Metadata Space Used: 4.039 MB
Metadata Space Total: 2.147 GB
Metadata Space Available: 2.143 GB
Udev Sync Supported: true
Deferred Removal Enabled: false
Deferred Deletion Enabled: false
Deferred Deleted Device Count: 0
Data loop file: /var/lib/docker/devicemapper/devicemapper/data
Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
Library Version: 1.02.77 (2012-10-15)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-71-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 1
Total Memory: 2.939 GiB
Name: mailgun-dev
ID: XTCU:ZBIE:2ISX:CRJY:23XC:YAPY:37ZJ:737S:BNVL:4IMT:BGXS:CPWX
WARNING: No swap limit support
It is still reproducible in 2.3.19
Just ran into this myself =)
Investigating...
-s
On Wed, Dec 30, 2015 at 2:53 PM, Maxim Vladimirskiy < notifications@github.com> wrote:
It is still reproducible in 2.3.19
— Reply to this email directly or view it on GitHub https://github.com/chef-cookbooks/docker/issues/572#issuecomment-168063989 .
@someara take a look over at #542. I have a feeling these two are related.
Verified with pry - https://gist.github.com/someara/2a7a06e2459a75f3612d#file-gistfile1-txt-L25 Adding coerce_hostname in a12066c58bbe6ab921db54754565b447018f1a9e Released as 2.3.20
had to revert 2.3.20... this is still broken as of 2.3.21.
Okay, we should be good to go in v2.3.22
Leave #542 open and I'll fix that when I return. There is a bigger issue with load_current_value and the properties of a container. Fixing this hostname issue as you did is more of just a bandaid. All the properties exhibit this same behavior.
I guess this would apply to all the network_mode validation properties as well.. dns, dns_search, mac_address, and extra_hosts
On Sat, Jan 2, 2016 at 7:12 PM, Chase Bolt notifications@github.com wrote:
Leave #542 https://github.com/chef-cookbooks/docker/issues/542 open and I'll fix that when I return. There is a bigger issue with load_current_value and the properties of a container. Fixing this hostname issue as you did is more of just a bandaid. All the properties exhibit this same behavior.
— Reply to this email directly or view it on GitHub https://github.com/chef-cookbooks/docker/issues/572#issuecomment-168441858 .
Let's track this in #542. Closing here.
Cookbook version: v2.3.5
When a running container that has
network_mode host
is reprovisioned the following error is reported: