Question Moving MariaDB and others to Docker.

Currently reading
Question Moving MariaDB and others to Docker.

I'm fed up with the fact that Synology apps are very rarely updated.
MariaDB is version 10.3.2 whilst the current version is 10.5.4.
When GDPR came into effect in the UK and I contacted Synology about an update I was basically ignored, despite the fact it meant anyone using MariaDB for any business data in the UK would be in breach.
I'm therefore looking to move from any Synology apps I can to Docker versions.
I thought I'd start with MariaDB. Does anyone have any information? I can see people have done it but they don't state which docker they chose from the registry, nor what environmental variables etc they used.
Any help would be greatly appreciated.
I'm using this for Kodi multiroom so will also be looking to create a headless Kodi install with the aim of automatically updating the database.
Welcome to the Forum!

I would suggest to start with the official mariadb image. If it lacks anything, you can still switch to an image of another trusted maintainer like or bitnami.

All of those image have a decent description that should provide a simple docker run example AND a description of all environment variables and required volumes.
Well that was much less painful than I'd anticipated. Configured users after I could connect to it.

There doesn't appear to be information as to how to update it when a new version is released, is there a way or will I have to backup and rebuild?
Last edited:
Glad it worked out so easy for you :)

I am not realy a mariadb user, so I can't realy tell much about the effect on updating the rdms.
Though, as long as the binary files are still compatible between versions and you did map a volume for the data folder, usualy its as simple as following this instructions.

Sidenote: a container is not a "docker", I never understood why people call it that... I guess this happens if non matter experts spread information to beginnerns. It always gives me an unpleasant feeling like if someone scratches chalk over a blackboard.
I didn't map a volume, I'm not sure how to (well I know how to, but I'm not sure what it would need to be mapped to). I'm very new to all of this and am not sure what I need to map a volume to for it to save the database in an area not tied entirely to the container. Thank you for your advice and help.

In the examples they use something like -v /path/on/host:/path/in/container to bind-mount a host folder (or just a single file) into a container path. The (left hand) side before the colon is always a host path OR a named volume (managed by docker, invisible to the Syno docker ui!) , the (right hand) side after the colon is the target path inside the container. Always use the container path as statet in the documentation, unless you know why you want to use a different path. In case of the official MariaDB image, it is ment to map a volume from the host (the ui has a file/folder picker for that) to the container path /var/lib/mysql.

This commandline -v option translates to the UI settings in the "volume tab". The setting can be configured in the extended settings when creating the container OR when you edit a stopped container. Though, be aware if you didn't have a mapping from the beginning and already worked with the container, your container will mount the mapped folder of the host on top of the folder in the container, which will result in previously existing files becomming invisible to the container.
Last edited:

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Welcome to! is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Similar threads