Service Name Portability

[t-lin]

Currently when creating and adding a service, one of the key params is the service-name. This service named is the human-readable component of the service, and is automatically coded into the list of CLI params for the proxy.

• e.g. If I run registry-cli add with a service name asdf, then the resulting image will hard-code asdf into the container's CMD as one of the parameters for the proxy.

If I then go to a new P2P network, run registry-cli add there with the -use-existing-image to pull it from Docker, but with a different service name (e.g. asdf2), then when that container starts, it'll try to find asdf from the new network's registry and fail to find it. This makes the service un-usable.

[t-lin]

Potential solution: Multi-Tier-Cloud/service-manager#60

If implemented, the registry-cli's auto-build process should be updated to ensure the new environment variable is picked up in the container images.