ARM架构下的Docker环境，OpenJDK官方没有8版本镜像，如何完美解决？

折腾了这么久，总算是完成了准备工作，接下来开始做作镜像了；

要把咱们自己的Java应用做成Docker镜像，需要有个JDK8镜像作为基础镜像，接下来我们来做这个基础镜像；

自己动手，做一个JDK8镜像

1. 在ARM电脑上新建一个文件夹，里面新建名为Dockerfile的文件，内容如下：

#Docker image of JDK8 in ARM64

VERSION 8

Author: bolingcavalry

#基础镜像使用的是OpenJDK官方镜像公用的

FROM buildpack-deps:stretch-scm

#作者

MAINTAINER BolingCavalry zq2599@gmail.com

Default to UTF-8 file.encoding

ENV LANG C.UTF-8

ENV JAVA_HOME /usr/local/jdk8

ENV PATH $JAV{A}_{H}OME/bin:$PATH

ENV JDK_FILE jdk-8u221-linux-arm64-vfp-hflt.tar.gz

COPY $JDK_FILE /usr/local/

RUN mkdir -p “$JAVA_HOME”; \

tar --extract \

–file /usr/local/$JDK_FILE \

–directory “$JAVA_HOME” \

–strip-components 1 \

–no-same-owner; \

rm /usr/local/$JDK_FILE

2. 将之前下载的jdk-8u221-linux-arm64-vfp-hflt.tar.gz文件复制到Dockerfile文件所在目录；

3. 在Dockerfile文件所在目录执行命令docker build -t bolingcavalry/arm64jdk:8 .（注意命令的末尾有个小数点，不要漏了）

4. 执行成功后控制台输出以下信息：

root@raspbian:~/test# docker build -t bolingcavalry/arm64jdk:8 .

Sending build context to Docker daemon 73.2MB

Step 1/8 : FROM buildpack-deps:stretch-scm

—> 1838b930d30a

Step 2/8 : MAINTAINER BolingCavalry zq2599@gmail.com

—> Using cache

—> ce7488aef612

Step 3/8 : ENV LANG C.UTF-8

—> Using cache

—> 0bdb9ce285a9

Step 4/8 : ENV JAVA_HOME /usr/local/jdk8

—> Using cache

—> 39a412f0d874

Step 5/8 : ENV PATH $JAV{A}_{H}OME/bin:$PATH

—> Using cache

—> 1a3077d36d4e

Step 6/8 : ENV JDK_FILE jdk-8u221-linux-arm64-vfp-hflt.tar.gz

—> Using cache

—> c39af69e10f7

Step 7/8 : COPY $JDK_FILE /usr/local/

—> Using cache

—> 5fc704c5b9ff

Step 8/8 : RUN mkdir -p "$JAV{A}_{H}OME";tar--extract--file/usr/local/$JDK_FILE --directory "$JAV{A}_{H}OME"--strip-components1--no-same-owner;rm/usr/local/$JDK_FILE

—> Running in a63663306adc

Removing intermediate container a63663306adc

—> ddc652d5dec0

Successfully built ddc652d5dec0

Successfully tagged bolingcavalry/arm64jdk:8

5. 验证一下效果：

root@raspbian:~/test# docker run --rm bolingcavalry/arm64jdk:8 java -version

java version “1.8.0_221”

Java™ SE Runtime Environment (build 1.8.0_221-b11)

Java HotSpot™ 64-Bit Server VM (build 25.221-b11, mixed mode)

把镜像推送到镜像仓库

将刚刚做好的镜像推送到仓库，这么做的原因如下：

1. 可以让大家使用到此镜像；

2. 接下来要用Jib插件将Java应用制作成镜像，Jib插件一定要从镜像仓库下载bolingcavalry/arm64jdk:8作为Java应用的基础镜像；

这里我将bolingcavalry/arm64jdk:8推送到了hub.docker.com，如果您没有hub.docker.com的账号，也可以选择推送到私有镜像仓库，只要是镜像仓库，Jib插件都支持；

将Java应用构建成镜像

1. 以前面提到的hellojib为例，打开pom.xml文件，将jib插件的配置改为如下内容：

com.google.cloud.tools

jib-maven-plugin

1.3.0

bolingcavalry/arm64jdk:8

bolingcavalry/hellojib:${project.version}

-Xms1g

-Xmx1g

8080

2. 执行命令mvn clean compile jib:dockerBui-U即可构建镜像，控制台输出如下信息（友情提示，这可能是个漫长的等待过程，我这等了9分多钟）：

root@raspbian:~/test/hellojib# mvn clean compile jib:dockerBuild -U

[INFO] Scanning for projects…

[INFO]

[INFO] ---------------------< com.bolingcavalry:hellojib >---------------------

[INFO] Building hellojib 0.0.1-SNAPSHOT

[INFO] --------------------------------[ jar ]---------------------------------

[INFO]

[INFO] — maven-clean-plugin:3.1.0:clean (default-clean) @ hellojib —

[INFO] Deleting /root/test/hellojib/target

[INFO]

[INFO] — maven-resources-plugin:3.1.0:resources (default-resources) @ hellojib —

[INFO] Using ‘UTF-8’ encoding to copy filtered resources.

[INFO] Copying 1 resource

[INFO] Copying 0 resource

[INFO]

[INFO] — maven-compiler-plugin:3.8.1:compile (default-compile) @ hellojib —

[INFO] Changes detected - recompiling the module!

[INFO] Compiling 2 source files to /root/test/hellojib/target/classes

[INFO]

[INFO] — jib-maven-plugin:1.3.0:dockerBuild (default-cli) @ hellojib —

[INFO]

[INFO] Containerizing application to Docker daemon as bolingcavalry/hellojib:0.0.1-SNAPSHOT…

[INFO] The base image requires auth. Trying again for bolingcavalry/arm64jdk:8…

[INFO]

[INFO] Container entrypoint set to [java, -Xms1g, -Xmx1g, -cp, /app/resources:/app/classes:/app/libs/*, com.bolingcavalry.hellojib.HellojibApplication]

[INFO]

[INFO] Built image to Docker daemon as bolingcavalry/hellojib:0.0.1-SNAPSHOT

[INFO] Executing tasks:

[INFO] [==============================] 100.0% complete

[INFO]

[INFO] ------------------------------------------------------------------------

[INFO] BUILD SUCCESS

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 09:59 min

[INFO] Finished at: 2019-10-02T19:42:42+08:00

[INFO] ------------------------------------------------------------------------

3. 验证hellojib工程的镜像是否正常，执行命令docker run --rm -p 8080:8080 bolingcavalry/hellojib:0.0.1-SNAPSHOT，控制台显示SpringBoot应用启动成功：

root@raspbian:~/test/hellojib# docker run --rm -p 8080:8080 bolingcavalry/hellojib:0.0.1-SNAPSHOT

. ____ _ __ _ _

/\ / _’ __ _ () __ __ _ \ \ \ \

( ( )___ | '_ | '| | ’ / _` | \ \ \ \

\/ _)| |)| | | | | || (| | ) ) ) )

’ || .__|| ||| |__, | / / / /

=|_|======|/=////

:: Spring Boot :: (v2.1.6.RELEASE)

2019-10-02 11:45:02.425 INFO 1 — [ main] c.b.hellojib.HellojibApplication : Starting HellojibApplication on d2d856d3c623 with PID 1 (/app/classes started by root in /)

2019-10-02 11:45:02.440 INFO 1 — [ main] c.b.hellojib.HellojibApplication : No active profile set, falling back to default profiles: default

2019-10-02 11:45:07.203 INFO 1 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http)

2019-10-02 11:45:07.342 INFO 1 — [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]

2019-10-02 11:45:07.344 INFO 1 — [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.21]

2019-10-02 11:45:07.761 INFO 1 — [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext

2019-10-02 11:45:07.762 INFO 1 — [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 5108 ms

2019-10-02 11:45:08.863 INFO 1 — [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Initializing ExecutorService ‘applicationTaskExecutor’

2019-10-02 11:45:10.027 INFO 1 — [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path ‘’

2019-10-02 11:45:10.037 INFO 1 — [ main] c.b.hellojib.HellojibApplication : Started HellojibApplication in 8.932 seconds (JVM running for 9.876)

2019-10-02 11:45:52.965 INFO 1 — [nio-8080-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring DispatcherServlet ‘dispatcherServlet’

2019-10-02 11:45:52.966 INFO 1 — [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet : Initializing Servlet ‘dispatcherServlet’

2019-10-02 11:45:52.993 INFO 1 — [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet : Completed initialization in 27 ms

4. ARM电脑的IP地址是192.168.50.118，因此在浏览器访问：http://192.168.50.118:8080/hello ，如下图，可见hellojib工程的容器可以正常工作，成功返回了数据：

SpringBoot工程终于在ARM机器的Docker环境下成功运行了，这里采用的是自制JDK8镜像的方式，还有一种方法也是可行的，即：使用OpenJDK官方的JDK11镜像；

使用OpenJDK官方的JDK11镜像

使用JDK11镜像，意味着Java工程所用的JDK从8升级到11，这个操作和Docker的关系不大，您只要验证应用在升级JDK后是否能运行正常即可，本文就不赘述了，我把自己在升级过程中遇到的问题列出来，帮您跳过小坑：

1. 从JDK9开始引入了module的概念，JDK8自带的一些jar包不再默认提供，您需要在应用的pom.xml中添加以下依赖，否则SpringBoot启动时会因为某些lass找不到导致启动失败：

javax.xml.bind

jaxb-api

2.3.1

com.sun.xml.bind

jaxb-impl

2.3.1

org.glassfish.jaxb

jaxb-runtime

2.3.1

2. 如果您的不想修改pom.xml，此时我的做法：

a. 将上述三个依赖对应的jar包全部找出来(注意这里绝不止三个jar包，还有它们的间接依赖)，放在ARM电脑的某个文件夹下面，例如/usr/local/extendJar;
b. 修改Jib插件的配置，增加一个classpath，例如：/usr/local/extendJar（注意这里的路径是容器内的）；
c. 在启动容器的时候，增加一个数据卷映射，将宿主机的/usr/local/extendJar映射到容器的/usr/local/extendJar；
至此，OpenJDK官方在ARM架构不提供8版本镜像的问题已完美解决，如果您正在使用ARM服务器做Docker+Java开发，希望此文能给您一些参考。