-
Notifications
You must be signed in to change notification settings - Fork 277
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
Problem with MySQL Docker: base image of mysql:8
is now Oracle based
#503
Comments
I'm wondering that ❯ docker run --rm -it mysql:8 cat /etc/os-release
Unable to find image 'mysql:8' locally
8: Pulling from library/mysql
Digest: sha256:a43f6e7e7f3a5e5b90f857fbed4e3103ece771b19f0f75880f767cf66bbb6577
Status: Downloaded newer image for mysql:8
NAME="Oracle Linux Server"
VERSION="8.7"
ID="ol"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="8.7"
PLATFORM_ID="platform:el8"
PRETTY_NAME="Oracle Linux Server 8.7"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:oracle:linux:8:7:server"
HOME_URL="https://linux.oracle.com/"
BUG_REPORT_URL="https://bugzilla.oracle.com/"
ORACLE_BUGZILLA_PRODUCT="Oracle Linux 8"
ORACLE_BUGZILLA_PRODUCT_VERSION=8.7
ORACLE_SUPPORT_PRODUCT="Oracle Linux"
ORACLE_SUPPORT_PRODUCT_VERSION=8.7 |
Think you're right, could be that I was using an old cached local image. Since docker-library/mysql#867 the default for After clearing the local mysql image, I now get
After changing the initial line to
|
mysql:8
is now Oracle based
Setup information
docker-compose build
(uncommented these lines)Describe the bug
It seems like the MySQL 8 image cannot be built. Running
docker-compose build
gives me:To reproduce
Steps to reproduce the behavior:
Expected behavior
Image should be buildable for folks wanting to use the backup functionallity.
Docker/Kubernetes/Helm:
docker version
:Possible fix/workaround:
Adding this line to the
config/mysql/Dockerfile
before runningapt-get update
:Additional info:
https://askubuntu.com/questions/1389928/mysql-an-error-occurred-during-the-signature-verification
The text was updated successfully, but these errors were encountered: