Most of the couchbase HTTP endpoints are not working when using the community-aarch64 docker image. I have tried exposing the ports, running docker in host networking mode, and even entering the container and using curl there - the results are the same regardless.
Based on the ports listed here, I have the following observations:
Port 8092 returns: {"couchdb":"Welcome"}
Ports 21100/21200/21300 hang for exactly 7 seconds and then give an empty reply
Port 4369 gives an empty reply immediately
Every other port listed (including the important 8091) gives “Connection refused” (or “Connection reset by peer” when exposed thru docker)
I would upload various log files, but this forum software doesn’t allow me. They are mostly filled with the same warning messages about various internal services failing to connect to http endpoints, for example:
./error.log:[ns_server:error,2022-05-21T11:26:22.088Z,ns_1@cb.local:ns_server_stats<0.7156.23>:ns_server_stats:handle_info:370]Received exit_status 1 from sigar
./error.log:[ns_server:error,2022-05-21T11:26:22.085Z,ns_1@cb.local:<0.7135.23>:prometheus:post_async:192]Prometheus http request failed: URL: http://127.0.0.1:9123/api/v1/query Body: <omitted> Reason: {failed_connect,[{to_address,{"127.0.0.1",9123}}, {inet,[inet],econnrefused}]}
./goxdcr.log:2022-05-21T10:28:29.396Z ERRO GOXDCR.TopoSvc: Original REST request (http://127.0.0.1:8091/pools/nodes) received "unknown pool" response. The URL may be incorrect or requested resource no longer exists
etc.
Of note:
I’m running Asahi Linux (ArchLinux ARM) on an M1 MacBook
If you need any additional information to diagnose this issue, please let me know.
Thanks,
Moulberry