-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Unable to deploy this apps on OpenShift #763
Comments
That's odd. I suspect the volume creates as a result of the VOLUME declaration ends up being read-only. Perhaps that's some strange OpenShift default permissions issue. |
It seems permission issue. workaround solutions provided here: docker-library/mysql#219 We are directly pulling docker image "weaveworksdemos/catalogue-db:0.3.0" but not creating any docker image as manually. apiVersion: extensions/v1beta1 |
Are you sure that will solve the problem? The catalogue-db k8s manifest isn't mounting any dirs from the host into the container. Nevertheless, to experiment, I suggest creating your own catalogue-db image. |
Let me try with 0.3.5 docker image https://hub.docker.com/r/weaveworksdemos/catalogue-db/tags/ |
I eventually deployed this application in OpenShift :) [root@master ~]# oc get pods Fix: I removed all the security context and run catalogue-db as user 0 Thanks for your support |
@coolpalani Can you share your yaml which you used it to deploy it to openshift |
Think i am getting a similar issue. What was the fix? Initializing database |
@coolpalani did you ever get this running on OpenShift? |
I am trying to deploy this micro service on OpenShift 3.7. It's throwing an error message while create catalogue-db pods
NAME READY STATUS RESTARTS AGE
catalogue-db-1846494424-2j29q 0/1 CrashLoopBackOff 6 8m
Error message
Initializing database
mysqld: Can't create/write to file '/var/lib/mysql/is_writable' (Errcode: 13 - Permission denied)
2018-03-14T13:11:18.115358Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-03-14T13:11:18.120035Z 0 [ERROR] --initialize specified but the data directory exists and is not writable. Aborting.
2018-03-14T13:11:18.120064Z 0 [ERROR] Aborting
The text was updated successfully, but these errors were encountered: