Okay, seems like there may be some bugs in Ping for that use case.
However, I may be able to offer an alternative, depending on your specific automated test use case. At CenterEdge, we use Docker for our automated test runs. In our case, Couchbase is a container, the service under test is a container, and the test suite itself is a container (plus sometimes some extra containers for other services).
For Couchbase, we created a special Docker image that supports full configuration on startup (buckets, indexes, fake data, etc) all based on declarative files that can be checked into source control. Once the initialization is complete, a file is written to disk on the container. If the folder is mapped between containers using a shared Docker volume, the other containers can watch for this file to know when Couchbase is up and running.
In case this helps, the system is available here: https://github.com/brantburnett/couchbasefakeit and there are images on Docker Hub for a lot of different Couchbase versions: https://hub.docker.com/r/btburnett3/couchbasefakeit. We use this approach extensively for automated functional testing almost all of our microservices as part of our CI/CD pipeline.