backend服务一直是unhealthy

[archguard]

backend服务一直是unhealthy

[phodal]

M1 比较麻烦，主要是 Docker 对于ARM 的支持问题。建议可以先试试本地 setup 开发环境

[awephy]

按照文档中https://archguard.org/development#macm1%E4%B8%AD%E5%A6%82%E4%BD%95%E8%BF%90%E8%A1%8C
在执行第二步，启动docker-compose时，报错container已存在

1. 第一步gradlew bootrun后的结果

2.第二步的截图（修改docker-compose文件确认按照文中的内容改过了）

[phodal]

估计得自己排查一下

[awephy]

已经解决了，感谢

[phodal]

如何解析？升级 Compose ？

[weiliang-ms]

我的是报下面的错误

Could not load hsdis-amd64.so; library not loadable; PrintAssembly is disabled

• docker版本

Client: Docker Engine - Community
 Version:           20.10.6
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        370c289
 Built:             Fri Apr  9 22:45:33 2021
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.14
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.16.15
  Git commit:       87a90dc
  Built:            Thu Mar 24 01:48:24 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.4.4
  GitCommit:        05f951a3781f4f2c1911b05e61c160e9c30eaa8e
 runc:
  Version:          1.0.0-rc93
  GitCommit:        12644e614e25b05da6fd08a38ffa0cfe1903fdec
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

• docker-compose版本

docker-compose version 1.29.2, build 5becea4c
docker-py version: 5.0.0
CPython version: 3.7.10
OpenSSL version: OpenSSL 1.1.0l  10 Sep 2019

• 系统版本

CentOS7.9

后台完整启动日志

archguard-backend     |
archguard-backend     |   .   ____          _            __ _ _
archguard-backend     |  /\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
archguard-backend     | ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
archguard-backend     |  \\/  ___)| |_)| | | | | || (_| |  ) ) ) )
archguard-backend     |   '  |____| .__|_| |_|_| |_\__, | / / / /
archguard-backend     |  =========|_|==============|___/=/_/_/_/
archguard-backend     |  :: Spring Boot ::               (v2.5.10)
archguard-backend     |
archguard-backend     | 2022-04-28 09:59:47.447  INFO 1 --- [           main] c.thoughtworks.archguard.ApplicationKt   : Starting ApplicationKt using Java 12-ea on b969fd02d246 with PID 1 (/home/spring/app.jar started by spring in /home/spring)
archguard-backend     | 2022-04-28 09:59:47.454  INFO 1 --- [           main] c.thoughtworks.archguard.ApplicationKt   : The following 1 profile is active: "debug"
archguard-backend     | 2022-04-28 09:59:47.457 DEBUG 1 --- [kground-preinit] o.h.v.i.xml.config.ValidationXmlParser   : Trying to load META-INF/validation.xml for XML based Validator configuration.
archguard-backend     | 2022-04-28 09:59:47.460 DEBUG 1 --- [kground-preinit] o.h.v.i.xml.config.ResourceLoaderHelper  : Trying to load META-INF/validation.xml via TCCL
archguard-backend     | 2022-04-28 09:59:47.461 DEBUG 1 --- [kground-preinit] o.h.v.i.xml.config.ResourceLoaderHelper  : Trying to load META-INF/validation.xml via Hibernate Validator's class loader
archguard-backend     | 2022-04-28 09:59:47.462 DEBUG 1 --- [kground-preinit] o.h.v.i.xml.config.ValidationXmlParser   : No META-INF/validation.xml found. Using annotation based configuration only.
archguard-backend     | 2022-04-28 09:59:47.473 DEBUG 1 --- [kground-preinit] o.h.v.i.e.resolver.TraversableResolvers  : Cannot find javax.persistence.Persistence on classpath. Assuming non JPA 2 environment. All properties will per default be traversable.
archguard-backend     | 2022-04-28 09:59:47.514 DEBUG 1 --- [kground-preinit] .h.v.m.ResourceBundleMessageInterpolator : Loaded expression factory via original TCCL
archguard-backend     | 2022-04-28 09:59:47.700 DEBUG 1 --- [kground-preinit] .i.e.ValidatorFactoryConfigurationHelper : HV000252: Using org.hibernate.validator.internal.engine.DefaultPropertyNodeNameProvider as property node name provider.
archguard-backend     | 2022-04-28 09:59:47.709 DEBUG 1 --- [kground-preinit] .i.e.ValidatorFactoryConfigurationHelper : HV000234: Using org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator as ValidatorFactory-scoped message interpolator.
archguard-backend     | 2022-04-28 09:59:47.710 DEBUG 1 --- [kground-preinit] .i.e.ValidatorFactoryConfigurationHelper : HV000234: Using org.hibernate.validator.internal.engine.resolver.TraverseAllTraversableResolver as ValidatorFactory-scoped traversable resolver.
archguard-backend     | 2022-04-28 09:59:47.710 DEBUG 1 --- [kground-preinit] .i.e.ValidatorFactoryConfigurationHelper : HV000234: Using org.hibernate.validator.internal.util.ExecutableParameterNameProvider as ValidatorFactory-scoped parameter name provider.
archguard-backend     | 2022-04-28 09:59:47.710 DEBUG 1 --- [kground-preinit] .i.e.ValidatorFactoryConfigurationHelper : HV000234: Using org.hibernate.validator.internal.engine.DefaultClockProvider as ValidatorFactory-scoped clock provider.
archguard-backend     | 2022-04-28 09:59:47.710 DEBUG 1 --- [kground-preinit] .i.e.ValidatorFactoryConfigurationHelper : HV000234: Using org.hibernate.validator.internal.engine.scripting.DefaultScriptEvaluatorFactory as ValidatorFactory-scoped script evaluator factory.
archguard-backend     | 2022-04-28 09:59:50.290  INFO 1 --- [           main] o.s.b.w.embedded.tomcat.TomcatWebServer  : Tomcat initialized with port(s): 8080 (http)
archguard-backend     | 2022-04-28 09:59:50.304  INFO 1 --- [           main] o.apache.catalina.core.StandardService   : Starting service [Tomcat]
archguard-backend     | 2022-04-28 09:59:50.304  INFO 1 --- [           main] org.apache.catalina.core.StandardEngine  : Starting Servlet engine: [Apache Tomcat/9.0.58]
archguard-backend     | #
archguard-backend     | # A fatal error has been detected by the Java Runtime Environment:
archguard-backend     | #
archguard-backend     | #  SIGILL (0x4) at pc=0x00007f8c63a0d9bc, pid=1, tid=8
archguard-backend     | #
archguard-backend     | # JRE version: OpenJDK Runtime Environment (12.0+29) (build 12-ea+29)
archguard-backend     | # Java VM: OpenJDK 64-Bit Server VM (12-ea+29, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
archguard-backend     | # Problematic frame:
archguard-backend     | # v  ~StubRoutines::updateBytesCRC32
archguard-backend     | #
archguard-backend     | # Core dump will be written. Default location: /home/spring/core.1
archguard-backend     | #
archguard-backend     | # An error report file with more information is saved as:
archguard-backend     | # /home/spring/hs_err_pid1.log
archguard-backend     | Could not load hsdis-amd64.so; library not loadable; PrintAssembly is disabled
archguard-backend     | #
archguard-backend     | # If you would like to submit a bug report, please visit:
archguard-backend     | #   http://bugreport.java.com/bugreport/crash.jsp
archguard-backend     | #

[phodal]

@weiliang-ms 你这个问题和 #47 是完全一样的，应该是 OpenJDK + 宿主机的问题

[hkcyl123]

我感觉是jdk的问题，因为m1版本的java 得用zulu 才能运行起来，而且我刚刚也查了一下，m1 docker打包出来的镜像默认是arm，我把代码clone下来后在本地启动时没问题的，所以估计要么是镜像问题，要么就是镜像内的java 环境问题

[phodal]

zulu 可以？要来个 PR 说明一下吗？https://github.com/archguard/archguard.org/blob/master/docs/setup/setup.md

[hkcyl123]

等我看看做成镜像后确认没问题，我把docker file PR进去

[hkcyl123]

毕竟docker 镜像会方便很多

[hkcyl123]

所以还是因为镜像本身不支持ARM架构的原因。

经过一下午的努力，终于搞定了。我一会提个PR

[phodal]

优秀