[
https://issues.apache.org/jira/browse/GRIFFIN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lionel Liu resolved GRIFFIN-99.
-------------------------------
Resolution: Done
It has been a long time from we solved this bug in current docker image now.
The bug comes from the OverlayFS of docker, which makes mysql startup fail. As
described here: [https://github.com/docker/for-linux/issues/72],
[https://github.com/geerlingguy/drupal-vm/issues/1497]
> Griffin - Docker - API server doesn't start as MySQL doesn't start on the
> docker container.
> -------------------------------------------------------------------------------------------
>
> Key: GRIFFIN-99
> URL: https://issues.apache.org/jira/browse/GRIFFIN-99
> Project: Griffin (Incubating)
> Issue Type: Bug
> Components: completeness-batch
> Affects Versions: 0.2.0-incubating
> Environment: Mac OSX
> Reporter: Akash Sharma S
> Assignee: Lionel Liu
> Priority: Critical
> Labels: SP_4
> Fix For: 0.2.0-incubating
>
>
> * I downloaded the docker images following the steps in the below page:
> **
> [https://github.com/apache/incubator-griffin/blob/master/griffin-doc/docker/griffin-docker-guide.md]
> * I'm bringing up the docker container using the docker compose file for
> batch mode.
>
> Observation:
> * I'm not able to access any of the APIs via the URL: <ip address>:38080
> * Upon further investigation, I found out after connecting to the docker
> container that MySQL isn't running inside the container, hence the API server
> isn't coming up.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
