Publish command fails for images built in-cluster

[eysi09]

Bug

Current Behavior

Running garden publish --env remote fails if the image hasn't been built locally. The reason is that the image name that is pulled doesn't match the image name that's published.

Expected behavior

Garden should publish the image.

Workaround

Publish the image from a local environment, e.g. garden publish my-module --env local for local refers to an environment that uses the local-kubernetes provider.

Suggested solution(s)

We need to re-tag the pulled imaged. Something like: docker tag pulledImage localId.