Share the journey of docker canal pitfalls (with solutions)

This article mainly shares with you the pitfall records of docker canal and introduces how to quickly solve these pitfalls. I hope it will be helpful to friends in need!

[Recommended learning: docker video tutorial]

Result

# #Potential pitfalls

• canal-server cannot connect to the database and prompts connection refuse.

• After canal-admin is started, start canal-server, and the admin log prompts connection refuse.

mac m1 Start canal-admin

docker run --platform linux/amd64 --name=canal-admin -e server.port=8089 -e canal.adminUser=admin -e canal.adminPasswd=123456 -p 8089:8089  -d canal/canal-admin:v1.1.5

The default password of canal-admin is admin. However, there is a bug in the admin panel, which only allows passwords of 6 digits and above, so the password is changed to 123456. However, after changing the password, it directly resulted in that after the canal-server was started, the panel did not display the started server.

The reason is because when canal-server starts: CanalServer and CanalAdmin will perform two-way authorization through CanalAdmin's login account and password. Therefore, the canal.admin.passwd specified when canal-server is started must be the 123456 encrypted password. You need to enter canal-admin and obtain the encrypted password of admin account 123456, which is used to start canal-server.

##mac m1 starts canal-server

docker run --platform linux/amd64 --name canal-server -p 11111:11111 -e canal.destinations=canal-server -e canal.auto.scan=false -e canal.destinations=canal-server -e canal.instance.master.address=192.168.0.102:3306 -e canal.instance.defaultDatabaseName=canal-server -e canal.instance.dbUsername=canal -e canal.instance.dbPassword=canal -e canal.admin.manager=192.168.0.102:8089 -e canal.admin.port=11110 -e canal.admin.user=admin -e canal.admin.passwd=6BB4837EB74329105EE4568DDA7DC67ED2CA2AD9 -e canal.instance.connectionCharset=UTF-8 -e canal.instance.tsdb.enable=true -e canal.instance.gtidon=false -d canal/canal-server:v1.1.5

There is another problem

When starting canal-server specifies canal.destinations=canal-server, but the client still prompts that canal-server should start first.

The solution is to manually add

The above is the detailed content of Share the journey of docker canal pitfalls (with solutions). For more information, please follow other related articles on the PHP Chinese website!