-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Add an ubuntu-base build #188
Conversation
build matrix is wrong. will fix that. |
I think this comment applies here as well. |
Also, you're installing the Ubuntu native 5.7 package, rather than the one from repo.mysql.com. While I'm fairly confident about the quality (I'm on the packaging team for the native packages), they will not be in sync with repo.mysql.com version-wise, and may have differences in the default configuration. |
@ltangvald I've failed to find the 5.7 version on the repo.mysql.com suited for the ubuntu xenial distro. can you please point me to this? |
5.7.12 was not released for Xenial on repo.mysql.com, as Xenial was released after 5.7.12, but 5.7.13 should be available as normal |
Found it here: http://repo.mysql.com/apt/ubuntu/pool/mysql-5.7/m/mysql-community/ |
in order to expose it to the host system if you want permission problems in other case
in order to expose it to the host system if you want permission problems in other case
same as here: docker-library#78 ``` [ERROR] --initialize specified but the data directory has files in it. Aborting. ```
I've just commented on docker-library/memcached#9 (comment) with a similar proposal. TLDR: it shouldn't matter what distro the images provide for a service like MySQL. With https://github.com/mysql/mysql-docker, the MySQL build team is providing Oracle Linux based images, and I had suggested slowly moving the images in this repo to be Oracle Linux only: #168 (comment). In summary, I am -1 on an Ubuntu based image, but would like to work toward merging |
Closing based on my last comment, but feel free to comment if you feel this was closed in error. |
It shouldn't but given the number of
|
As you can see from the Debian Security Team's notes below, the majority of these are either minor issues, not security issues, or do not apply, so the reason the list is so long is exactly because the Debian Security Team is so diligent, coupled with the security scanning tools not parsing the (admittedly somewhat free-form) metadata appropriately to tag these properly in the same way that RedHat would mark them "WONTFIX", for example. It is definitely untrue to imply that the Debian Security Team is any less aggressive or proactive than that of Ubuntu (in fact, there's even overlap on the teams, given Ubuntu is based on Debian, so it's in their best interest to make sure the problems are resolved in Debian as well).
https://bugs.debian.org/776268
https://bugs.debian.org/778950
https://bugs.debian.org/628843 (not fixed upstream, AFAICT) https://bugs.debian.org/841856 (also not fixed upstream, AFAICT) |
@tianon I appreciate the thorough response.
This is down to a lack of insight on my behalf. I've been tasked with securing a load of images by ensuring that no |
https://github.com/docker-library/faq#why-does-my-security-scanner-show-that-an-image-has-cves is probably also useful |
Only the last LTS ubuntu release xenial is supported, and only the mysql 5.7 version that xenial natively supports.