Skip to content

Commit 8f6dc37

Browse files
authored
Merge pull request #52 from oracle/issue-51
update doc with details of the need to accept image license on docker…
2 parents b2b8a5b + 180ec10 commit 8f6dc37

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

site/creating-domain.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,9 +43,13 @@ kubectl create secret docker-registry SECRET_NAME
4343

4444
In this command, replace the uppercase items with the appropriate values. The `SECRET_NAME` will be needed in later parameter files. The `NAMESPACE` must match the namespace where the first domain will be deployed, otherwise Kubernetes will not be able to find it. It is generally easier to manually pull the image in advance, as described in the next section.
4545

46+
## Go to the Docker Store and accept the license agreement for the WebLogic Server image
47+
48+
If you have never used the WebLogic Server image before, you will need to go to the [Docker Store web interface](https://store.docker.com/images/oracle-weblogic-server-12c) and accept the license agreement before Docker Store will allow you to pull this image. This is a one-time requirement, you do not have to repeat it for each machine you want to use the image on.
49+
4650
## Pull the WebLogic Server image
4751

48-
You can let Kubernetes pull the Docker image for you the first time you try to create a pod that uses the image, but we have found that you can generally avoid various common issues like putting the secret in the wrong namespace or getting the credentials wrong by just manually pulling the image by running these commands *on the Kubernetes master*:
52+
You can let Kubernetes pull the Docker image for you the first time you try to create a pod that uses the image, but we have found that you can generally avoid various common issues like putting the secret in the wrong namespace or getting the credentials wrong by just manually pulling the image by running these commands *on the Kubernetes nodes*:
4953

5054
```
5155
docker login

0 commit comments

Comments
 (0)