MariaDB installed directly onto the OS and not in docker container

  • After a successfully installation of a new OMV5 server, I want to keep the installation simple and clean and not to add multiple layers especially using docker containers. It will be used only for Shared Folders in local network and DB server for KODI player.


    In this case, please let me know if you recommend the manually installation of the MariaBD SQL Sever directly into the OS like any other Debian package instead of docker container.


    What are the concerns about this approach?


    Thank you.

    The Power of the Power Button!
    OMV 4.x // Hardware: HP N36L Microserver (BIOS mod), 4GB RAM, 2x1TB WD Red + 2x2TB ST, 160GB for OMV

    OMV 5.x // Hardware: HP Microserver Gen8, 4GB RAM, 2x4TB WD + 2x2TB ST, 160GB for OMV

  • Sorry, but nobody has an opinion about installing the MariaBD SQL Sever directly into the OS?

    Can will interfere with other OMV configurations?


    Thanks.

    The Power of the Power Button!
    OMV 4.x // Hardware: HP N36L Microserver (BIOS mod), 4GB RAM, 2x1TB WD Red + 2x2TB ST, 160GB for OMV

    OMV 5.x // Hardware: HP Microserver Gen8, 4GB RAM, 2x4TB WD + 2x2TB ST, 160GB for OMV

  • It won't interfere with your OpenMediaVault configuration since it doesn't use MySQL/MariaDB.


    So if you want to avoid the docker layer, since you're not feeling for it, install it on your host instead.


    Greetings

    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • in my opinion ( and is only a opinion), docker is the way.


    do not add any complexity or workload, and is easy to deploy.

  • Hi all,


    Thank you for your opinions. I will go with installing MariaDB directly on the host.

    For me, even if I work in IT, to use containerization just for a simple data base for my KODI player, will imply additional work for maintaining a complicated solution for a little and simple thing.


    I use OMV for more then 4 years now, since ver. 2, and I like it especially because it's simple, robust and easy to maintain.

    And for that I wish for all developers and maintainers all the best for their good work.


    Good luck!

    The Power of the Power Button!
    OMV 4.x // Hardware: HP N36L Microserver (BIOS mod), 4GB RAM, 2x1TB WD Red + 2x2TB ST, 160GB for OMV

    OMV 5.x // Hardware: HP Microserver Gen8, 4GB RAM, 2x4TB WD + 2x2TB ST, 160GB for OMV

  • Docker is maintained automatically if you use solutions like watchtower which update containers automagically.

    Once a container is set, it works and you forget it's in Docker.


    Moreover, the less you install in the main OS, less likely an upgrade or something else will screw up.

    OMV BUILD - MY NAS KILLER - OMV 5.x + omvextrasorg


    Core i3-8300 - ASRock H370M-ITX/ac - 8GB RAM - Sandisk Ultra Flair 32GB (OMV), 256GB NVME SSD (Docker), 3x4TB HDD (Data) - Fractal Design Node 304 - Be quiet! Pure Power 11 350W

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!