myesn commented on issue #3166:
URL: 
https://github.com/apache/incubator-shenyu/issues/3166#issuecomment-1091685221

   Very understand that you are busy with exams, but can other project members 
help me look at this problem (database and shenyu services run on arm64 
architecture)?
   
   I tried it all day today, using the `v2.4.2 tag` and deploying it with 
Docker-Compose, but things didn't go well. I replaced the base Docker Image for 
shenyu-bootstrap and shenyu-admin with `openjdk:8u322-jre`, and there was 
another new problems: 
   
   1. Because the `db` service image does not support arm64 architecture, I 
used `biarms/mysql:5.7.30-linux-arm64v8` as a replacement, and it seems to work 
fine
   2.  `shenyu-admin` service's `spring.profiles.active=mysql environment` 
variable configuration no longer works, I used `SPRING_PROFILES_ACTIVE=mysql` 
to replace it and it works
   3. The log of the `shenyu-admin` service has an error that the database 
cannot be connected: 
       Communications link failure(The last packet sent successfully to the 
server was 0 milliseconds ago. The driver has not received any packets from the 
server)
   
   But when I use the source code of `v2.4.2 tag` to run locally, the above 
errors do not appear, so I want to debug by printing some logs in the source 
code, but I don't know how the release profile works. I modified the source 
code, but there is no newly added code in the tar.gz file of the final release. 
I tried my best. I have been doing this all day today. The Raspberry Pi 
executes `mvn -Prelease`, and the docker is also very, very good. Slow, it 
takes more than ten minutes each time. I really want to introduce this gateway 
product in our company, but at present, in terms of deployment, the `database`, 
`shenyu bootstrap` and ` shenyu admin` cannot run well on the `arm64` 
architecture. I Hope you guys can help me with these issues, I'd be more than 
happy to assist you with testing!
   
   Thanks!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to