Create multiple releases of mariadb-alpine?

[Luc45]

Howdy, is mysqldump available in this image? Would it add too much size to add it?

[Luc45]

Opened a PR to see how many kbs it adds to the image: #229

[jbergstroem]

Thanks for opening the PR! As you also see; finding the middle ground between functionality and minimalism is hard.

Seeing how this is more of a client tool rather than server; I'm really on the fence.

[jbergstroem]

Old topic: mysqldump is not included?

I took the liberty of moving this issue to a discussion. The topic is "which tools would a extended version of the container include".

[jbergstroem]

How I see this:

• I would like to keep the baseline / default release as small as possible which would be as-is (including a client). The core purpose is to distribute a working server
• The extended tag would contain additional binaries. What I'd consier at this point: mysqldump, mysqladmin, aria_chk, myisamchk, mysqlcheck, mysql_upgrade (from mariadb-server-utils) and mysql_tzinfo_to_sql.

Thoughts?

Edit: added mysql_tzinfo_to_sql to simplify the tz population.

[jbergstroem]

The goal of this project is to optimize for size, not for feature parity. There are lots of containers that gives you a fully fledged mariadb setup with all tools you need; I don't see the reason to create another one.

[Luc45]

I agree with @jbergstroem here. The main point of this image is the size. About which programs to include, it would be nice to know the size of each in kb to decide.

[jbergstroem]

, it would be nice to know the size of each in kb to decide.

Would you say that size is still important in the -extended or -tools or w/e we end up calling it?

[williamdes]

-tools would make sense

[williamdes]

the list looks correct