Notes for Docker Installations Using GCP

The following section are additional notes for Docker installations using GCP.

  • Init logs for the containers (ML-CM, in particular) under /var/log/mashery/ are your most helpful way for troubleshooting why a container may not be fully initializing. For example, looking at these logs were used to determine that while a key/secret were being passed to MOM for authentication, the process was ultimately failing. This may have been due to explicitly defining a MOM-Host during the set-mom-secret script process. Deleting the existing secret, and re-creating/replacing it, helped the container to initialize without issues.
  • During initialization of the containers you may, almost immediately, see warnings or errors of persistent volume health checks failing. This is caused by health-check scripts running a little too quickly, which draws these flags. Give the containers a little more time (2 to 4 minutes on average for a decently equipped K8s cluster). You can refresh your dashboard or check "kubectl get pods" to see if all 4 containers come on line. The ML-CM (4th container) tends to take a little longer than the rest.