Ubuntu 14.04 default docker is 1.0, which emits float memory sizes about registrator HOT 7 CLOSED

Alright. Not sure how to test it, but the next release should be using that version of dockerclient...

from registrator.

If you want to test it, a very simple way is via shipyard. See referenced closed ticket.

from registrator.

I'm seeing the very same thing via these error messages -

2014/12/15 15:00:01 registrator: unable to inspect container: f7c5587e633d json: cannot unmarshal number 6.7108864e+07 into Go value of type int64

When launching containers from inside the Mesos Marathon Framework.

from registrator.

Consider upgrading your registrator container; latest builds of registrator include a newer version of fsouza/go-docker which have resolved the problem for me.

from registrator.

Are you sure? As I build from a fresh docker image from the registry (also using 'latest' build tag - which should be 0.4.0). Also still in master branch of the git repo - https://github.com/progrium/registrator/blob/master/Godeps/_workspace/src/github.com/fsouza/go-dockerclient/container.go#L161-L162

Also this issue is still open, which suggests its not resolved? Although it looks like it should be since the PR above was merged in July? Though I am fairly new to docker/registrator so maybe I am doing something wrong on my end.

from registrator.

This: https://github.com/progrium/registrator works correctly for me.

You raised some good points so I decided to dig in a bit deeper.

Seems that the old float values I could see for memory (using docker inspect) are now integer values!
This appears to have happened after I upgraded docker from 1.3.1 to 1.3.2 (using the lxc-docker deb package in ubuntu).

It seems that this was resolved some time ago: moby/moby#6246
and seems to be handled in the docker code: https://github.com/docker/docker/blob/master/engine/env.go#L230-L234

but perhaps it only got included in 1.3.2.

What is the docker version you are running?

from registrator.

Yup, Doh, I was running docker 1.0.1 (for some reason), after upgrading to docker 1.4.0 the issue is resolved. Thanks for the help investigating!

from registrator.