-
Notifications
You must be signed in to change notification settings - Fork 27
Description
Description:
When an alpine image from docker.wso2.com is pulled during docker-compose up, was able to observe the following error and couldn't up the OB-KM server.
docker-compose up
Pulling obkm (docker.wso2.com/wso2-obkm:1.4.0.1590163412537.7-alpine3.10)...
1.4.0.1590163412537.7-alpine3.10: Pulling from wso2-obkm
9d48c3bd43c5: Pull complete
617745506915: Pull complete
b0ed4aba78d0: Pull complete
7c4093696c4e: Pull complete
d3e097d210be: Pull complete
2305320c8cee: Pull complete
b8a1c87ad1fe: Pull complete
ac370eb2b69c: Pull complete
e55eae32bdd9: Pull complete
9152d811fef2: Pull complete
mysql is up-to-date
Creating obkm ... done
Attaching to mysql, obkm
obkm | env: can't execute 'bash': No such file or directory
mysql | Initializing database
mysql | 2020-06-02T11:30:10.266857Z 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
mysql | 2020-06-02T11:30:10.443615Z 0 [Warning] InnoDB: New log files created, LSN=45790
Affected Product Version:
1.4.0
Steps to reproduce:
- Follow the instructions given in [1].
- Change the docker-compose.yml in [2] to pull an alpine image.
- Run "docker-compose up".
[1] - https://github.com/wso2/docker-open-banking/blob/1.4.x/docker-compose/obkm/README.md
[2] - https://github.com/wso2/docker-open-banking/blob/1.4.x/docker-compose/obkm/docker-compose.yml