51255feb1b
* Using upacked Spring layers for faster boot * Added option to pass JAVA_OPT to modify the environment variables in both flavours * Build support for different hawkbit apps - could be used in future if hawkBit is split in multiple micro-services * Removed templates and replacing with parameterized (via build ARGs) docker builds Signed-off-by: Marinov Avgustin <Avgustin.Marinov@bosch.com>
hawkBit Docker
Build files for both hawkbit docker flavours - standard (no mysql driver) and mysql (with MariaDB Java connector with support for MySQL).
Build overview
Images are built using Dockerfile or Dockerfile-mysql. They accept ARG build parameters JAVA_VERSION, HAWKBIT_APP (by default hawkbit-update-server), HAWKBIT_VERSION_ (by default the last released hawkBit version), CONTAINER_PORT (by default 8080) on which the app opens the http server (if available) and (for mysql flavour only) MARIADB_DRIVER_VERSION (by default 3.1.4 at the time of writing). Both flavours of are almost the same, just mysql has in addition a MariaDB Java connector and is started, by default, with mysql Spring profile.
Build standard
Standard flavour could be build, for example, with:
docker build --build-arg HAWKBIT_APP=hawkbit-update-server -t hawkbit_update_server:0.3.0 . -f Dockerfile
or just by:
docker build --build-arg HAWKBIT_APP=hawkbit-update-server -t hawkbit_update_server:0.3.0 .
having that docker uses by default Dockerfile.
Build mysql
Mysql flavour could be build, for example, with:
docker build --build-arg HAWKBIT_APP=hawkbit-update-server -t hawkbit_update_server:0.3.0-mysql . -f Dockerfile-mysql