-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest Build doesn't work (Based on alpine 3.9) #2
Comments
I noticed that you modfied the Dockerfile by adding the tag "latest" but I think that I misspoke - maybe my English is not good enough (I'm French) I found that when the image is created since "alpine-micro 3.9/latest", it is not possible to connect to the databases. On the other hand, if I modify the dockerfile by specifying the "3.8" tag for the "alpine-micro" version, the image is functional again. So there is a problem of configuration of mariadb with "alpine-micro 3.9" that makes the image unusable but I can not say which one. If that helps, you'll find below the logs from an "alpine-mariadb" image used with docker-compose Wordpress. " |
On which platform are you using?
I'll do some more test on other platforms |
I use it on a Fedore Server, version 27 but up to date. Docker is in version 18.09 (the last available). I have not tried starting from a blank base, I only work with my existing base. I use the image as well on the host as for my different site and service and all via docker-compose. When I use the alpine-micro 3.9 based image, connection to the database is impossible. mysql -h 127.0.0.1 -u root -p |
Because you are using "alpine-micro" without a tag version in your Dockerfile file, the latest version of this container does not work and you can not connect to the database.
I rebuilt the container, specifying "alpine-micro: 3.8" and the contenter obtained works again.
The text was updated successfully, but these errors were encountered: