Comment by Alex Suter on tuannv's answer

Alex Suter — Thu, 07 Nov 2019 04:04:18 -0500

please accept answer ;)

Answer by tuannv

tuannv — Thu, 07 Nov 2019 03:34:14 -0500

Thank you every much. you're right I build it success full

Answer by Alex Suter

Alex Suter — Thu, 07 Nov 2019 02:23:09 -0500

Your Dockerfile has some interesting stuff in it.

1) MAINTAINER is depreacted

2) The official axonivy-engine image is a linux based image. It makes no sense to create any windows-style folders in your image. Creating paths like that E:/Axon7.4/AxonIvyDesigner7.4.0.1909161423_Windows_x64/workspace/mytest/Portal/makes no sense at all.

3) There is no need to change to rights of the deploy folder. The deploy folder belongs to the ivy user which is part of the container.

4) Adding your *.iar file to the the special windows folder in the container has no effect.

5) ADD target/mytest-1.0.0-SNAPSHOT.iar deploy seems to work partly, but you need at least to set the correct user and group of the deployed file with --chown=ivy:ivy.

6) Exposing port 8080 in your Dockerfile is not needed, this is already done by the base image (axonivy-engine).

I think your file should look more like this:

FROM axonivy/axonivy-engine:7.4.0
LABEL maintainer="tuan.nguyen@axonactive.com"

ADD --chown=ivy:ivy target/mytest-1.0.0-SNAPSHOT.iar deploy

For more information have a look at the Dockerfile of the axonivy/axonivy-engine image and the example how to deploy an application to the engine (this is similar to an ivy archive).

Answers to: Docker container can't apply IAR newest

Comment by Alex Suter on tuannv's answer

Answer by tuannv

Answer by Alex Suter