Cloud API Overview > @adpt/cloud > docker > RegistryDockerImageProps > registryUrl

docker.RegistryDockerImageProps.registryUrl property

URL or string for the registry where the image should be pushed and pulled

Signature:

registryUrl: string | DockerSplitRegistryInfo;

Remarks

If this parameter is a string, registryUrl will be used for both push and pull

If registryUrl is of the form { external: string, internal: string }, docker images wil be pushed to external and image strings will refer to internal.

Note(manishv) This is a bit of a hack to allow one hostname or IP address to push images from outside a particular environment (say k8s) and a different URL for that environment to pull images.

A good example of this is a k3s-dind (k3s docker-in-docker) instance of kubernetes where a private registry is running on a docker network attached to the k3s-dind instance, but where we want to push docker.LocalDockerImage built images to that registry. Since LocalDockerImage is outside the k3s-dind environment, it must use a host accessible network to push to the registry. However, since the k3s-dind instance sees the registry from within Docker, it must use a different address to pull the images for use.

Once network scopes are fully supported, this interface will change to whatever is appropriate. It is best if you can arrange to have the same URL or registry string work for all access regardless of which network the registry, Adapt host, and ultimate container running environment is uses.