Comment 4 for bug 907908

I think it's fair to say that most people use some form of configuration management to keep the nodes within a cluster consistent, so assuming that a remote host will have a similar config to the current host is reasonable.

If you really don't want to use the values in the local config, please change the output so that it doesn't appear to be a copy/pastable command; instead use natural language eg "The object is in containers/56319/f5c/dbff743f38ec090aaad93c4da3666f5c/ on 10.0.0.123".

Creating a command that is clearly intended to be copied to the shell that hard codes a configurable element just seems like it's teasing. The output transparently mixes accurate information (the host and path within the container) with information it has no right to assume is correct (the absolute path to the container directory). This mix is not indicated in any way and is a trap.