@@ -21,22 +21,22 @@ Please note that the first build takes time, but subsequent runs add merely ```~
2121
2222```
2323mvn package -Pthorntail && unzip target/mp-starter-hollow-thorntail.jar -d target/mp-starter-hollow-thorntail
24- docker build -f Container/Dockerfile -t microprofile/start.microprofile.io:1.0-SNAPSHOT .
24+ docker build -f Container/Dockerfile -t microprofile/start.microprofile.io:0.8 .
2525```
2626
2727Run locally
2828-----------
2929
3030```
31- docker run -p 127.0.0.1:8080:8080/tcp -d -i --name mp-starter microprofile/start.microprofile.io:1.0-SNAPSHOT
31+ docker run -p 127.0.0.1:8080:8080/tcp -d -i --name mp-starter microprofile/start.microprofile.io:0.8
3232docker stop -t 2 mp-starter && docker rm mp-starter
3333```
3434
3535Push image to registry and restart service
3636------------------------------------------
3737
3838```
39- docker push microprofile/start.microprofile.io:1.0-SNAPSHOT
39+ docker push microprofile/start.microprofile.io:0.8
4040ssh ec2-user@aws-microstarter "sudo systemctl restart [email protected] " 4141```
4242
@@ -47,8 +47,8 @@ Example flow
4747
4848```
4949mvn package -Pthorntail && unzip target/mp-starter-hollow-thorntail.jar -d target/mp-starter-hollow-thorntail
50- docker build -f Container/Dockerfile -t microprofile/start.microprofile.io:1.0-SNAPSHOT .
51- docker push microprofile/start.microprofile.io:1.0-SNAPSHOT
50+ docker build -f Container/Dockerfile -t microprofile/start.microprofile.io:0.8 .
51+ docker push microprofile/start.microprofile.io:0.8
5252ssh ec2-user@aws-microstarter "sudo systemctl restart [email protected] " 5353```
5454
@@ -70,16 +70,16 @@ Refactoring the app so as it runs just with a plain servlet container is a possi
7070
7171Building an image
7272-----------------
73- Note the tag ``` microprofile/start.microprofile.io:1.0-SNAPSHOT ``` is an example and you should use your own namespace.
73+ Note the tag ``` microprofile/start.microprofile.io:0.8 ``` is an example and you should use your own namespace.
7474
7575```
76- docker build -f Container/Dockerfile.CI -t microprofile/start.microprofile.io:1.0-SNAPSHOT .
76+ docker build -f Container/Dockerfile.CI -t microprofile/start.microprofile.io:0.8 .
7777```
7878
7979One can push the built image to a public DockerHub (one needs an account though):
8080
8181```
82- docker push microprofile/start.microprofile.io:1.0-SNAPSHOT
82+ docker push microprofile/start.microprofile.io:0.8
8383```
8484
8585Running a container locally
@@ -96,7 +96,7 @@ docker run -e MY_LOGLEVEL=INFO \
9696 -e MY_MX_HEAP="512m" \
9797 -e MY_META_SPACE="96M" \
9898 -e MY_MAX_META_SPACE="256m" \
99- -p 127.0.0.1:8080:8080/tcp -d -i --name mp-starter microprofile/start.microprofile.io:1.0-SNAPSHOT
99+ -p 127.0.0.1:8080:8080/tcp -d -i --name mp-starter microprofile/start.microprofile.io:0.8
100100```
101101
102102One can watch the logs:
@@ -116,13 +116,13 @@ Debugging the image build
116116One can skip the final stage of the multistage build and just do the first stage:
117117
118118```
119- docker build --target build-env -f Container/Dockerfile.CI -t microprofile/start.microprofile.io:1.0-SNAPSHOT .
119+ docker build --target build-env -f Container/Dockerfile.CI -t microprofile/start.microprofile.io:0.8 .
120120```
121121
122122You can start bash and look around without starting the application:
123123
124124```
125- docker run -i --entrypoint=/bin/bash --name mp-starter microprofile/start.microprofile.io:1.0-SNAPSHOT
125+ docker run -i --entrypoint=/bin/bash --name mp-starter microprofile/start.microprofile.io:0.8
126126```
127127
128128If you have the container running already and you want to examine it, you can:
@@ -159,7 +159,7 @@ cat /etc/docker/compose/mp-starter/docker-compose.yml
159159version: '3'
160160services:
161161 mp-starter:
162- image: "microprofile/start.microprofile.io:1.0-SNAPSHOT "
162+ image: "microprofile/start.microprofile.io:0.8 "
163163 user: wildfly
164164 ports:
165165 - 443:8443
0 commit comments