vac

Closed this one as it is discussed in https://github.com/apitable/apitable/issues/347.

@bytesnackscgn Please verify the network connectivity between containers: ```text $ docker compose exec -it room-server bash root@35f65c3d6087:/app# curl mysql:3306 curl: (1) Received HTTP/0.9 when not allowed root@35f65c3d6087:/app# curl redis:6379 curl:...

@bytesnackscgn Sorry. The log messages you provided are not from init-appdata. If you modified the .env please run `docker compose up -d` to make it effective.

Yes. Maybe we should only retry the `docker compose pull` step so much times. The main reason for that loop is that dockerhub is not very stable (i.e. for users...

> @networkhermit How about considering use `curl -I https://hub.docker.com/` then catch status code to avoid the failed-retry branch？ No. That's not a reliable way to retry image pulling, as it...

Don't use Windows drive when running `make dataenv` in WSL.

@JosephTLyons hello, is there any update about this issue? The `Open in Terminal` action on folders in the project panel would also opens two terminal instances. Besides, is it possible...

> @JosephTLyons > > hello, is there any update about this issue? > > The `Open in Terminal` action on folders in the project panel would also opens two terminal...

> Hi @networkhermit, are you still interested in working on this one? If you need any help, feel free to reach out. I don't think there is established consensus among...

> @networkhermit are you still experiencing this issue? If you want to try curl, don't forget to add `-L` as the API redirects directly to github: > > ```shell >...