The version of Nebula Studio is v3.7.0, the kernel version is v3.5.0, and it is deployed as a Windows standalone using Docker Desktop for installation.
After installing nebula-docker-compose, all containers start normally without any problems. However, every time the computer is restarted and all containers are started through Docker Desktop, I immediately encounter an error when attempting to log in. Previously, the solution was to wait ten minutes for all containers to start and then enter through the console. But today, even after waiting for about an hour, I still cannot enter through the console, and restarting Docker Desktop does not help. The related meta / storage / graph info log information is as follows:
2023-06-28 15:11:38 goroutine 1 [running]:
2023-06-28 15:11:38 log.Panicf(0xc0001b60c0, 0xbb, 0x0, 0x0, 0x0)
2023-06-28 15:11:38 /usr/local/go/src/log/log.go:345 +0xc0
2023-06-28 15:11:38 main.main()
2023-06-28 15:11:38 /usr/src/main.go:532 +0xb0b
2023-06-28 15:11:39 2023/06/28 07:11:39 Fail to initialize the connection pool, host: graphd, port: 9669, failed to open connection, error: failed to open transport, error: dial tcp 172.18.0.4:9669: connect: connection refused
2023-06-28 15:11:39 panic: Fail to initialize the connection pool, host: graphd, port: 9669, failed to open connection, error: failed to open transport, error: dial tcp 172.18.0.4:9669: connect: connection refused
Note 1: The difference between this problem and the console container not running in nebula-docker-compose after the computer is restarted is that the console can be logged in to.
However, I cannot log in to Nebula using any method.
Note 2: Because all previous deployments were on the local machine and used the same IP address without a VPN, the IP address should not be entered incorrectly.
How can I solve this problem?
