Skip to content

Commit e108f14

Browse files
committed
fix(registry): explain PORT is required when using private registry information
1 parent 4fced10 commit e108f14

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

src/applications/using-docker-images.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,11 @@ tool like [jq][] and then used in the password field in `deis registry:set`. For
7878
deis registry:set username=_json_key password="$(cat google_cloud_cred.json | jq -c .)"
7979
```
8080

81+
When using a private registry the docker images are no longer pulled into the Deis Internal Registry via
82+
the Deis Workflow Controller but rather is managed by Kubernetes. This will increase security and overall speed,
83+
however the `port` information can no longer be discovered. Instead the `port` information can be set via
84+
`deis config:set PORT=80` prior to setting the registry information.
85+
8186
**NOTE:**
8287
Currently [GCR.io][] and [ECR][] in short lived auth token mode are not supported.
8388

0 commit comments

Comments
 (0)