The Docker service inspector looks at image meta data to work out if there is a single target port exposed. This currently fails if the image does not exist on the node that Honeycomb is running on.
Additionally, it seems that only the repository name is being used to lookup the image, not the tag name - obviously ports could change between image tags so this needs to be taken into account.
There is a simple workaround: applying the honeycomb.port=<n> label to the service bypasses the image inspection altogether.
The Docker service inspector looks at image meta data to work out if there is a single target port exposed. This currently fails if the image does not exist on the node that Honeycomb is running on.
Additionally, it seems that only the repository name is being used to lookup the image, not the tag name - obviously ports could change between image tags so this needs to be taken into account.
There is a simple workaround: applying the
honeycomb.port=<n>label to the service bypasses the image inspection altogether.