Skip to content

Commit 0b152de

Browse files
committed
updates from bob
1 parent ffaa3a4 commit 0b152de

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

site/developer.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,8 @@ To run the operator in a Kubernetes cluster, you need to build the Docker image
129129
After you have run the build (that is, `mvn clean install`), create the Docker image as follows:
130130

131131
```
132-
docker build -t weblogic-kubernetes-operator:some-tag --no-cache=true .
132+
docker build -t weblogic-kubernetes-operator:some-tag \
133+
--build-arg VERSION=2.0-SNAPSHOT --no-cache=true .
133134
```
134135

135136
We recommend that you use a tag other than `latest` to make it easy to distinguish your image from the "real" one. In the example above, we used the GitHub ID of the developer.
@@ -144,7 +145,7 @@ scp operator.tar YOUR_USER@YOUR_SERVER:/some/path/operator.tar
144145
docker load < /some/path/operator.tar
145146
```
146147

147-
Verify that you have the right image by running `docker images | grep webloogic-kubernetes-operator` on both machines and comparing the image IDs.
148+
Verify that you have the right image by running `docker images | grep weblogic-kubernetes-operator` on both machines and comparing the image IDs.
148149

149150
To create and deploy the operator, first, make a copy of the inputs file (`create-weblogic-operator-inputs.yaml`) and update it, making sure that `weblogicOperatorImagePullPolicy` is set to `Never` and `weblogicOperatorImage` matches the name you used in your `docker build` command.
150151

0 commit comments

Comments
 (0)